You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

39 lines
2.2 KiB

  1. # Contributing guidelines
  2. ## How to become a contributor and submit your own code
  3. ### Environment setup
  4. It is recommended to use filter to manage the GitHub email notification, see [examples for setting filters to Kubernetes Github notifications](https://github.com/kubernetes/community/blob/master/communication/best-practices.md#examples-for-setting-filters-to-kubernetes-github-notifications)
  5. To install development dependencies you can set up a python virtual env with the necessary dependencies:
  6. ```ShellSession
  7. virtualenv venv
  8. source venv/bin/activate
  9. pip install -r tests/requirements.txt
  10. ```
  11. #### Linting
  12. Kubespray uses `yamllint` and `ansible-lint`. To run them locally use `yamllint .` and `ansible-lint`. It is a good idea to add call these tools as part of your pre-commit hook and avoid a lot of back end forth on fixing linting issues (<https://support.gitkraken.com/working-with-repositories/githooksexample/>).
  13. #### Molecule
  14. [molecule](https://github.com/ansible-community/molecule) is designed to help the development and testing of Ansible roles. In Kubespray you can run it all for all roles with `./tests/scripts/molecule_run.sh` or for a specific role (that you are working with) with `molecule test` from the role directory (`cd roles/my-role`).
  15. When developing or debugging a role it can be useful to run `molecule create` and `molecule converge` separately. Then you can use `molecule login` to SSH into the test environment.
  16. #### Vagrant
  17. Vagrant with VirtualBox or libvirt driver helps you to quickly spin test clusters to test things end to end. See [README.md#vagrant](README.md)
  18. ### Contributing A Patch
  19. 1. Submit an issue describing your proposed change to the repo in question.
  20. 2. The [repo owners](OWNERS) will respond to your issue promptly.
  21. 3. Fork the desired repo, develop and test your code changes.
  22. 4. Sign the CNCF CLA (<https://git.k8s.io/community/CLA.md#the-contributor-license-agreement>)
  23. 5. Submit a pull request.
  24. 6. Work with the reviewers on their suggestions.
  25. 7. Ensure to rebase to the HEAD of your target branch and squash un-necessary commits (<https://blog.carbonfive.com/always-squash-and-rebase-your-git-commits/>) before final merger of your contribution.