mirror of https://github.com/kubernetes/kops.git
commit
39ef6433a2
14
README.md
14
README.md
|
|
@ -92,10 +92,10 @@ What this means:
|
|||
__Issues__
|
||||
* Help read and triage issues, assist when possible.
|
||||
* Point out issues that are duplicates, out of date, etc.
|
||||
- Even if you don't have tagging permissions, make a note and tag maintainers. (`/close`,`/dupe #127`)
|
||||
- Even if you don't have tagging permissions, make a note and tag maintainers (`/close`,`/dupe #127`).
|
||||
|
||||
__Pull Requests__
|
||||
* Read and review the code. Leave comments, questions, and critiques (`/lgtm` )
|
||||
* 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.
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ You can check your week number using:
|
|||
date +%V
|
||||
```
|
||||
|
||||
The maintainers and other community members are generally available on the [kubernetes slack](https://github.com/kubernetes/community#slack-chat) in [#kops](https://kubernetes.slack.com/messages/kops/), so come find and chat with us about how kops can be better for you!
|
||||
The maintainers and other community members are generally available on the [kubernetes slack](https://github.com/kubernetes/community/blob/master/communication.md#social-media) in [#kops](https://kubernetes.slack.com/messages/kops/), so come find and chat with us about how kops can be better for you!
|
||||
|
||||
|
||||
## GitHub Issues
|
||||
|
|
@ -147,17 +147,17 @@ 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 `-v 10` 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
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new)
|
||||
- Note the version of kops you are running (from `kops version`), and the command line options you are using.
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new).
|
||||
- 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](https://github.com/kubernetes/community#slack-chat)
|
||||
- Feel free to reach out to the kops community on [kubernetes slack](https://github.com/kubernetes/community/blob/master/communication.md#social-media).
|
||||
|
||||
|
||||
### Features
|
||||
|
||||
We also use the issue tracker to track features. If you have an idea for a feature, or think you can help kops become even more awesome follow the steps below.
|
||||
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new)
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new).
|
||||
- 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 `this` 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.
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@
|
|||
* [Example on how to add a feature](development/adding_a_feature.md)
|
||||
* [Hack Directory](development/hack.md)
|
||||
* [How to update `kops` API](development/api_updates.md)
|
||||
* [Low level description on how kops works](how_it_works.md)
|
||||
* [Low level description on how kops works](development/how_it_works.md)
|
||||
* [Notes on Gossip design](development/gossip.md)
|
||||
* [Notes on master instance sizing](development/instancesizes.md)
|
||||
* [Our release process](development/release.md)
|
||||
|
|
|
|||
|
|
@ -327,19 +327,18 @@ metadata:
|
|||
spec:
|
||||
```
|
||||
|
||||
Full documentation is accessible via [godocs] (https://godoc.org/k8s.io/kops/pkg/apis/kops#InstanceGroupSpec).
|
||||
Full documentation is accessible via [godocs](https://godoc.org/k8s.io/kops/pkg/apis/kops#InstanceGroupSpec).
|
||||
|
||||
Instance Groups map to auto scale groups in AWS, and Instance Groups in GCE. They are an API level description of a group of compute instances used as Masters or Nodes.
|
||||
Instance Groups map to Auto Scaling Groups in AWS, and Instance Groups in GCE. They are an API level description of a group of compute instances used as Masters or Nodes.
|
||||
|
||||
More documentation is available in the [Instance Group](instance_groups.md) document.
|
||||
|
||||
## Closing Thoughts
|
||||
|
||||
Using YAML or JSON-based configuration for building and managing kops clusters is powerful, but use with caution.
|
||||
Using YAML or JSON-based configuration for building and managing kops clusters is powerful, but use this strategy with caution.
|
||||
|
||||
- If you do not need to define or customize a value, let kops set that value
|
||||
Setting too many values dont allow kops to do its job in setting up the cluster and you may end up with strange bugs
|
||||
- If you end up with strange bugs, try letting kops do more
|
||||
- If you do not need to define or customize a value, let kops set that value. Setting too many values prevents kops from doing its job in setting up the cluster and you may end up with strange bugs.
|
||||
- If you end up with strange bugs, try letting kops do more.
|
||||
- Be cautious, take care, and test test test outside of production!
|
||||
|
||||
If you need to run a custom version of Kubernetes Controller Manager, set `kubeControllerManager.image` and update your cluster, and that is the beauty of using a manifest for your cluster.
|
||||
If you need to run a custom version of Kubernetes Controller Manager, set `kubeControllerManager.image` and update your cluster. This is the beauty of using a manifest for your cluster!
|
||||
|
|
|
|||
Loading…
Reference in New Issue