Getting Involved and Contributing

In the interest of getting more newer folks involved with kOps, we are starting to tag issues with . These are typically issues that have smaller scope but are good ways to start to get acquainted with the codebase.

We also encourage ALL active community participants to act as if they are maintainers, even if you don’t have “official” write permissions. This is a community effort, we are here to serve the Kubernetes community. If you have an active interest and you want to get involved, you have real power! Don’t assume that the only people who can get things done around here are the “maintainers”.

We also would love to add more “official” maintainers, so show us what you can do!

Issues

• Help read and triage issues, assist when possible.

Pull Requests

• Read and review the code. Leave comments, questions, and critiques (/lgtm ).
• Download, compile, and run the code and make sure the tests pass (make test).
  • Also verify that the new feature seems sane, follows best architectural patterns, and includes tests.

This repository uses the Kubernetes bots. See a full list of the commands here.

For more information, checkout the

Please check in with us in the #kops-users or channel. Often-times, a well crafted question or potential bug report in slack will catch the attention of the right folks and help quickly get the ship righted.

If you think you have found a bug please follow the instructions below.

• Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
• Set command line option and save the log output. Please paste this into your issue.
• Note the version of kOps you are running (from kops version), and the command line options you are using.
• Remember users might be searching for your issue in the future, so please give it a meaningful title to helps others.
• Feel free to reach out to the kOps community on kubernetes slack.

• Open a .
• Remember users might be searching for your issue in the future, so please give it a meaningful title to helps others.
• Clearly define the use case, using concrete examples. EG: I type and kOps does that.
• Some of our larger features will require some design. If you would like to include a technical design for your feature please include it in the issue.
• After the new feature is well understood, and the design agreed upon we can start coding the feature. We would love for you to code it. So please open up a WIP (work in progress) pull request, and happy coding.