kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Broken Links fix for 2696 (#3171) 

* broken links fix in kubernetes community

* Broken Links bug fix

* Implemented Review Comments

* Implemented Review Comments
This commit is contained in:
ramnar 2019-02-05 20:14:42 +05:30 committed by Kubernetes Prow Robot
parent 2e3d0dce64
commit a095f16dc8
4 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
contributors/guide/github-workflow.md
View File

@ -199,7 +199,7 @@ git push -f ${your_remote_name} myfeature
### 7 Create a pull request ### 7 Create a pull request
1. Visit your fork at https://github.com/$user/kubernetes 1. Visit your fork at `https://github.com/$user/kubernetes`
2. Click the `Compare & Pull Request` button next to your `myfeature` branch. 2. Click the `Compare & Pull Request` button next to your `myfeature` branch.
3. Check out the pull request [process](/contributors/guide/pull-requests.md) for more details and 3. Check out the pull request [process](/contributors/guide/pull-requests.md) for more details and
advice. advice.
@ -219,10 +219,6 @@ Commit changes made in response to review comments to the same branch on your
fork. fork.
Very small PRs are easy to review. Very large PRs are very difficult to review. Very small PRs are easy to review. Very large PRs are very difficult to review.
At the assigned reviewer's discretion, a PR may be switched to use
[Reviewable](https://reviewable.k8s.io) instead. Once a PR is switched to
Reviewable, please ONLY send or reply to comments through Reviewable. Mixing
code review tools can be very confusing.
#### Squash and Merge #### Squash and Merge

2
sig-azure/charter.md
View File

@ -97,4 +97,4 @@ Issues impacting multiple subprojects in the SIG should be resolved by SIG Techn
[super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote [super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote
[KEP]: https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md [KEP]: https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454 [sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454
[OWNERS]: contributors/devel/owners.md [OWNERS]: /contributors/guide/owners.md

4
sig-multicluster/CONTRIBUTING.md
View File

@ -275,8 +275,8 @@ See the sig-multicluster [community page] for points of contact and meeting time
[community page]: /sig-multicluster [community page]: /sig-multicluster
[contributors guide]: /contributors/guide [contributors guide]: /contributors/guide
[design proposal]: #design-proposals [design proposal]: #design-proposals
[design repo]: /contributors/design-proposals/sig-multicluster [design repo]: /contributors/design-proposals/multicluster
[design template]: /contributors/design-proposals/sig-multicluster/template.md [design template]: /contributors/design-proposals/Design_Proposal_TEMPLATE.md
[development guide]: /contributors/devel/development.md [development guide]: /contributors/devel/development.md
[existing issue]: #adopt-an-issue [existing issue]: #adopt-an-issue
[feature repo]: https://github.com/kubernetes/features [feature repo]: https://github.com/kubernetes/features

2
sig-storage/contributing.md
View File

@ -40,7 +40,7 @@ For folks looking to add support for a new storage platform in Kubernetes, you h
- Write an in-tree volume plugin or provisioner: You can contribute a new in-tree volume plugin or provisioner, that gets built and ships with Kubernetes, for use within the Persistent Volume Framework. - Write an in-tree volume plugin or provisioner: You can contribute a new in-tree volume plugin or provisioner, that gets built and ships with Kubernetes, for use within the Persistent Volume Framework.
[See the Ceph RBD volume plugin example](https://git.k8s.io/kubernetes/pkg/volume/rbd) or [the AWS Provisioner example](https://github.com/kubernetes/kubernetes/pull/29006) [See the Ceph RBD volume plugin example](https://git.k8s.io/kubernetes/pkg/volume/rbd) or [the AWS Provisioner example](https://github.com/kubernetes/kubernetes/pull/29006)
- Write a FlexVolume plugin: This is an out-of-tree volume plugin which you develop and build separately outside of Kubernetes. - Write a FlexVolume plugin: This is an out-of-tree volume plugin which you develop and build separately outside of Kubernetes.
You then install the plugin on every Kubernetes host within your cluster and then [configure the plugin in Kubernetes as a FlexVolume](https://git.k8s.io/kubernetes/examples/volumes/flexvolume) You then install the plugin on every Kubernetes host within your cluster and then [configure the plugin in Kubernetes as a FlexVolume](https://git.k8s.io/examples/staging/volumes/flexvolume)
- Write a Provisioner Controller: You can write a separate controller that watches for pending claims with a specific selector label on them. - Write a Provisioner Controller: You can write a separate controller that watches for pending claims with a specific selector label on them.
Once an appropriate claim is discovered, the controller then provisions the appropriate storage intended for the claim and creates a corresponding Once an appropriate claim is discovered, the controller then provisions the appropriate storage intended for the claim and creates a corresponding
persistent volume for the claim that includes the same label used in the original claim selector. This will ensure that the PV for the new persistent volume for the claim that includes the same label used in the original claim selector. This will ensure that the PV for the new