├── .github ├── CODEOWNERS └── ISSUE_TEMPLATE.md ├── CODE_OF_CONDUCT.md ├── MAINTAINERS └── README.md /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @balopat @nkubala @kimsterv @priyawadhwa 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 4 | 5 | ### Use case description 6 | 7 | e.g: 8 | - we are a team of 10 engineers working on a microservices system (~5 microservices) 9 | - we are using kubernetes for deployment, minikube locally, on-prem for testing and GKE for staging and prod 10 | - ... 11 | 12 | ### Pain points 13 | 14 | Setting up the microservices integration tests end to end is our biggest pain point, because... 15 | ... -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of 9 | experience, education, socio-economic status, nationality, personal appearance, 10 | race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or reject 41 | comments, commits, code, wiki edits, issues, and other contributions that are 42 | not aligned to this Code of Conduct, or to ban temporarily or permanently any 43 | contributor for other behaviors that they deem inappropriate, threatening, 44 | offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | This Code of Conduct also applies outside the project spaces when the Project 56 | Steward has a reasonable belief that an individual's behavior may have a 57 | negative impact on the project or its community. 58 | 59 | ## Conflict Resolution 60 | 61 | We do not believe that all conflict is bad; healthy debate and disagreement 62 | often yield positive results. However, it is never okay to be disrespectful or 63 | to engage in behavior that violates the project’s code of conduct. 64 | 65 | If you see someone violating the code of conduct, you are encouraged to address 66 | the behavior directly with those involved. Many issues can be resolved quickly 67 | and easily, and this gives people more control over the outcome of their 68 | dispute. If you are unable to resolve the matter for any reason, or if the 69 | behavior is threatening or harassing, report it. We are dedicated to providing 70 | an environment where participants feel welcome and safe. 71 | 72 | Reports should be directed to the maintainers, the Project Steward(s) for 73 | Skaffold. It is the Project Steward’s duty to receive and address reported 74 | violations of the code of conduct. They will then work with a committee 75 | consisting of representatives from the Open Source Programs Office and the 76 | Google Open Source Strategy team. If for any reason you are uncomfortable 77 | reaching out the Project Steward, please email opensource@google.com. 78 | 79 | We will investigate every complaint, but you may not receive a direct response. 80 | We will use our discretion in determining when and how to follow up on reported 81 | incidents, which may range from not taking action to permanent expulsion from 82 | the project and project-sponsored spaces. We will notify the accused of the 83 | report and provide them an opportunity to discuss it before any action is taken. 84 | The identity of the reporter will be omitted from the details of the report 85 | supplied to the accused. In potentially harmful situations, such as ongoing 86 | harassment or threats to anyone's safety, we may take action without notice. 87 | 88 | ## Attribution 89 | 90 | This Code of Conduct is adapted from the Contributor Covenant, version 1.4, 91 | available at 92 | https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 93 | -------------------------------------------------------------------------------- /MAINTAINERS: -------------------------------------------------------------------------------- 1 | Balint Pato 2 | Nick Kubala 3 | Priya Wadhwa 4 | Kim Lewandowski -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # KIT 2 | 3 | # Kubernetes Integration Testing 4 | 5 | As systems grow, integration testing is not easy to get right and the complexity of Kubernetes definitely makes things harder. We want to change that! 6 | 7 | We are looking to start a conversation in the open with teams that are running or planning to run their systems on Kubernetes and facing integration testing and end-to-end testing problems. 8 | 9 | What are your major pain points? If you had a magic wand that could create magical integration test solutions - what features would you like to see? Open a ticket! Spread the word! Let's have a conversation! 10 | 11 | # What is this repo? 12 | 13 | This is a "teaser" repository where you can let your voices heard and we can use it as a source of real feedback from the community around real needs. 14 | 15 | We will not have code here (at least for a while) but we will have proposals and discussions (issues). 16 | 17 | The process is simple: 18 | 19 | - open an issue to start a discussion around an idea, your use case or a problem definition 20 | - if the discussion identifies a clear use case - we will collect it in `use-cases/` folder 21 | 22 | Structure of the repo: 23 | 24 | ``` 25 | use-cases\ 26 | README.md - this file 27 | ``` 28 | 29 | 30 | # When can we see some real software? 31 | 32 | In 2019 :) 33 | --------------------------------------------------------------------------------