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

fix: use https:// instead of http://

This commit is contained in:
Junya Okabe 2024-06-09 02:22:43 +09:00
parent fd7bc7aadf
commit 0adfecd04d
11 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md
View File

@ -2325,6 +2325,6 @@ Twitter | [Sep 19th](https://twitter.com/stephenaugustus/status/1174797710043430
* bentheelder - Shoutout to @jeefy for the really shiny and useful looking structured Kubernetes release notes viewer demo in today's #sig-release meeting, looking forward to seeing more about this! * bentheelder - Shoutout to @jeefy for the really shiny and useful looking structured Kubernetes release notes viewer demo in today's #sig-release meeting, looking forward to seeing more about this!
* Maria - shoutout to Silvia Moura Pina (@smourapina) for putting together a workflow to enable the CI signal subteam of the release team keep on top of flagging issues from e2e tests and coordinate follow-ups and to Jorge Alarcon (@Jorge) for spotting an opportunity to offer broader transparency to what the CI signal team is working on, suggesting a structure and kicking off implementation (find current version at [https://github.com/orgs/kubernetes/projects/11](https://github.com/orgs/kubernetes/projects/11)) * Maria - shoutout to Silvia Moura Pina (@smourapina) for putting together a workflow to enable the CI signal subteam of the release team keep on top of flagging issues from e2e tests and coordinate follow-ups and to Jorge Alarcon (@Jorge) for spotting an opportunity to offer broader transparency to what the CI signal team is working on, suggesting a structure and kicking off implementation (find current version at [https://github.com/orgs/kubernetes/projects/11](https://github.com/orgs/kubernetes/projects/11))
* spiffxp - shouts to Josh Berkus (@jberkus) for taking notes during today’s steering committee meeting, our google doc clearly becomes way more difficult to use with so many people looking at it, and the written record is invaluable * spiffxp - shouts to Josh Berkus (@jberkus) for taking notes during today’s steering committee meeting, our google doc clearly becomes way more difficult to use with so many people looking at it, and the written record is invaluable
* spiffxp - shoutout to Katharine Berry (@Katharine) for moving us from gubernator to spyglass for all of our test result viewing needs! [http://sigs.k8s.io/prow/pkg/spyglass ](http://sigs.k8s.io/prow/pkg/spyglass) * spiffxp - shoutout to Katharine Berry (@Katharine) for moving us from gubernator to spyglass for all of our test result viewing needs! [https://sigs.k8s.io/prow/pkg/spyglass ](https://sigs.k8s.io/prow/pkg/spyglass)
* codenrhoden - Shoutout to Michelle Au (@msau42) for her patience and helpful guidance in getting a very large PR merged! * codenrhoden - Shoutout to Michelle Au (@msau42) for her patience and helpful guidance in getting a very large PR merged!
* @strebel - @jeefy and @onyiny-ang for all their awesome work on the Release-Notes team for 1.14. Especially @jeefy’s work on the Release-Notes website concept * @strebel - @jeefy and @onyiny-ang for all their awesome work on the Release-Notes team for 1.14. Especially @jeefy’s work on the Release-Notes website concept

2
contributors/devel/automation.md
View File

@ -9,7 +9,7 @@ processes.
## Tide ## Tide
This project formerly used a Submit Queue, it has since been replaced by This project formerly used a Submit Queue, it has since been replaced by
[Tide](http://sigs.k8s.io/prow/cmd/tide). [Tide](https://sigs.k8s.io/prow/cmd/tide).
### Ready to merge status ### Ready to merge status

2
contributors/devel/sig-testing/e2e-tests.md
View File

@ -644,7 +644,7 @@ A quick overview of how we run e2e CI on Kubernetes.
We run a battery of [release-blocking jobs](https://testgrid.k8s.io/sig-release-master-blocking) We run a battery of [release-blocking jobs](https://testgrid.k8s.io/sig-release-master-blocking)
against `HEAD` of the master branch on a continuous basis, and block merges against `HEAD` of the master branch on a continuous basis, and block merges
via [Tide](http://sigs.k8s.io/prow/cmd/tide) on a subset of those via [Tide](https://sigs.k8s.io/prow/cmd/tide) on a subset of those
tests if they fail. tests if they fail.
CI results can be found at [ci-test.k8s.io](http://ci-test.k8s.io), e.g. CI results can be found at [ci-test.k8s.io](http://ci-test.k8s.io), e.g.

2
contributors/devel/sig-testing/testing.md
View File

@ -229,7 +229,7 @@ If the failure seems unrelated to the change you're submitting:
- if you don't get a response in 24 hours, engage with the SIG on their channel on the [Kubernetes slack](http://slack.k8s.io/) and/or attend one of the [SIG meetings][sig-meetings] to ask for input. - if you don't get a response in 24 hours, engage with the SIG on their channel on the [Kubernetes slack](http://slack.k8s.io/) and/or attend one of the [SIG meetings][sig-meetings] to ask for input.
[prow-url]: https://prow.k8s.io [prow-url]: https://prow.k8s.io
[prow-git]: http://sigs.k8s.io/prow/pkg [prow-git]: https://sigs.k8s.io/prow/pkg
[prow-doc]: https://kubernetes.io/blog/2018/08/29/the-machines-can-do-the-work-a-story-of-kubernetes-testing-ci-and-automating-the-contributor-experience/#enter-prow [prow-doc]: https://kubernetes.io/blog/2018/08/29/the-machines-can-do-the-work-a-story-of-kubernetes-testing-ci-and-automating-the-contributor-experience/#enter-prow
[membership]: https://github.com/kubernetes/community/blob/master/community-membership.md#member [membership]: https://github.com/kubernetes/community/blob/master/community-membership.md#member
[k-teams]: https://github.com/orgs/kubernetes/teams [k-teams]: https://github.com/orgs/kubernetes/teams

20
contributors/guide/owners.md
View File

@ -22,7 +22,7 @@ of OWNERS files.
## OWNERS spec ## OWNERS spec
The [k8s.io/test-infra/prow/repoowners package](http://sigs.k8s.io/prow/pkg/repoowners/repoowners.go) The [k8s.io/test-infra/prow/repoowners package](https://sigs.k8s.io/prow/pkg/repoowners/repoowners.go)
is the main consumer of OWNERS files. If this page is out of date, look there. is the main consumer of OWNERS files. If this page is out of date, look there.
### OWNERS ### OWNERS
@ -253,20 +253,20 @@ Kubernetes uses the Prow Blunderbuss plugin and Tide.
Tide uses GitHub queries to select PRs into “tide pools”, runs as many in a Tide uses GitHub queries to select PRs into “tide pools”, runs as many in a
batch as it can (“tide comes in”), and merges them (“tide goes out”). batch as it can (“tide comes in”), and merges them (“tide goes out”).
- [Blunderbuss plugin](http://sigs.k8s.io/prow/pkg/plugins/blunderbuss): - [Blunderbuss plugin](https://sigs.k8s.io/prow/pkg/plugins/blunderbuss):
- responsible for determining **reviewers** - responsible for determining **reviewers**
- [Tide](http://sigs.k8s.io/prow/cmd/tide): - [Tide](https://sigs.k8s.io/prow/cmd/tide):
- responsible for automatically running batch tests and merging multiple PRs together whenever possible. - responsible for automatically running batch tests and merging multiple PRs together whenever possible.
- responsible for retriggering stale PR tests. - responsible for retriggering stale PR tests.
- responsible for updating a GitHub status check explaining why a PR can't be merged (eg: a - responsible for updating a GitHub status check explaining why a PR can't be merged (eg: a
missing `lgtm` or `approved` label) missing `lgtm` or `approved` label)
### [`prow`](http://sigs.k8s.io/prow/pkg) ### [`prow`](https://sigs.k8s.io/prow/pkg)
Prow receives events from GitHub, and reacts to them. It is effectively stateless. The following Prow receives events from GitHub, and reacts to them. It is effectively stateless. The following
pieces of prow are used to implement the code review process above. pieces of prow are used to implement the code review process above.
- [cmd: tide](http://sigs.k8s.io/prow/cmd/tide) - [cmd: tide](https://sigs.k8s.io/prow/cmd/tide)
- per-repo configuration: - per-repo configuration:
- `labels`: list of labels required to be present for merge (eg: `lgtm`) - `labels`: list of labels required to be present for merge (eg: `lgtm`)
- `missingLabels`: list of labels required to be missing for merge (eg: `do-not-merge/hold`) - `missingLabels`: list of labels required to be missing for merge (eg: `do-not-merge/hold`)
@ -278,10 +278,10 @@ pieces of prow are used to implement the code review process above.
- merges PR's once they meet the appropriate criteria as configured above - merges PR's once they meet the appropriate criteria as configured above
- if there are any presubmit prow jobs for the repo the PR is against, they will be re-run one - if there are any presubmit prow jobs for the repo the PR is against, they will be re-run one
final time just prior to merge final time just prior to merge
- [plugin: assign](http://sigs.k8s.io/prow/pkg/plugins/assign) - [plugin: assign](https://sigs.k8s.io/prow/pkg/plugins/assign)
- assigns GitHub users in response to `/assign` comments on a PR - assigns GitHub users in response to `/assign` comments on a PR
- unassigns GitHub users in response to `/unassign` comments on a PR - unassigns GitHub users in response to `/unassign` comments on a PR
- [plugin: approve](http://sigs.k8s.io/prow/pkg/plugins/approve) - [plugin: approve](https://sigs.k8s.io/prow/pkg/plugins/approve)
- per-repo configuration: - per-repo configuration:
- `issue_required`: defaults to `false`; when `true`, require that the PR description link to - `issue_required`: defaults to `false`; when `true`, require that the PR description link to
an issue, or that at least one **approver** issues a `/approve no-issue` an issue, or that at least one **approver** issues a `/approve no-issue`
@ -291,12 +291,12 @@ pieces of prow are used to implement the code review process above.
OWNERS files has `/approve`'d OWNERS files has `/approve`'d
- comments as required OWNERS files are satisfied - comments as required OWNERS files are satisfied
- removes outdated approval status comments - removes outdated approval status comments
- [plugin: blunderbuss](http://sigs.k8s.io/prow/pkg/plugins/blunderbuss) - [plugin: blunderbuss](https://sigs.k8s.io/prow/pkg/plugins/blunderbuss)
- determines **reviewers** and requests their reviews on PR's - determines **reviewers** and requests their reviews on PR's
- [plugin: lgtm](http://sigs.k8s.io/prow/pkg/plugins/lgtm) - [plugin: lgtm](https://sigs.k8s.io/prow/pkg/plugins/lgtm)
- adds the `lgtm` label when a **reviewer** comments `/lgtm` on a PR - adds the `lgtm` label when a **reviewer** comments `/lgtm` on a PR
- the **PR author** may not `/lgtm` their own PR - the **PR author** may not `/lgtm` their own PR
- [pkg: k8s.io/test-infra/prow/repoowners](http://sigs.k8s.io/prow/pkg/repoowners/repoowners.go) - [pkg: k8s.io/test-infra/prow/repoowners](https://sigs.k8s.io/prow/pkg/repoowners/repoowners.go)
- parses OWNERS and OWNERS_ALIAS files - parses OWNERS and OWNERS_ALIAS files
- if the `no_parent_owners` option is encountered, parent owners are excluded from having - if the `no_parent_owners` option is encountered, parent owners are excluded from having
any influence over files adjacent to or underneath of the current OWNERS file any influence over files adjacent to or underneath of the current OWNERS file

2
contributors/guide/pull-requests.md
View File

@ -595,7 +595,7 @@ Once the tests pass, and the reviewer adds the `lgtm` and `approved` labels, the
The merge pool is needed to make sure no incompatible changes have been introduced by other pull requests since the tests were last run on your pull request. The merge pool is needed to make sure no incompatible changes have been introduced by other pull requests since the tests were last run on your pull request.
<!-- TODO: create parallel instructions for reviewers --> <!-- TODO: create parallel instructions for reviewers -->
[Tide](http://sigs.k8s.io/prow/cmd/tide) will manage the merge pool [Tide](https://sigs.k8s.io/prow/cmd/tide) will manage the merge pool
automatically. It uses GitHub queries to select PRs into “tide pools”, automatically. It uses GitHub queries to select PRs into “tide pools”,
runs as many in a batch as it can (“tide comes in”), and merges them (“tide goes out”). runs as many in a batch as it can (“tide comes in”), and merges them (“tide goes out”).

2
contributors/guide/review-guidelines.md
View File

@ -145,7 +145,7 @@ git checkout foo
[KEEP THE SPACE SHUTTLE FLYING]: https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/volume/persistentvolume/pv_controller.go#L57-L117 [KEEP THE SPACE SHUTTLE FLYING]: https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/volume/persistentvolume/pv_controller.go#L57-L117
[commit message guidelines]: ./pull-requests.md#7-commit-message-guidelines [commit message guidelines]: ./pull-requests.md#7-commit-message-guidelines
[GitHub Status]: https://help.github.com/en/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#setting-a-status [GitHub Status]: https://help.github.com/en/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#setting-a-status
[Blunderbuss]: http://sigs.k8s.io/prow/pkg/plugins/approve/approvers/ [Blunderbuss]: https://sigs.k8s.io/prow/pkg/plugins/approve/approvers/
[emeritus_approver]: ./owners.md#emeritus [emeritus_approver]: ./owners.md#emeritus
[Keeping the Bar High - How to be a bad ass Code Reviewer, Tim Hockin]: https://www.youtube.com/watch?v=OZVv7-o8i40 [Keeping the Bar High - How to be a bad ass Code Reviewer, Tim Hockin]: https://www.youtube.com/watch?v=OZVv7-o8i40
[Kubernetes Code Reviewing with Tim Hockin]: https://docs.google.com/document/d/15y8nIgWMzptHcYIeqf4vLJPttE3Fj_ht4I6Nj4ghDLA/edit#heading=h.3dchnigrxf5y [Kubernetes Code Reviewing with Tim Hockin]: https://docs.google.com/document/d/15y8nIgWMzptHcYIeqf4vLJPttE3Fj_ht4I6Nj4ghDLA/edit#heading=h.3dchnigrxf5y

2
contributors/guide/style-guide.md
View File

@ -635,7 +635,7 @@ relative links. However, how and what they're being linked to can vary widely.
``` ```
The super cool [prow tool] resides in the test-infra repo under the kubernetes organization The super cool [prow tool] resides in the test-infra repo under the kubernetes organization
[prow tool]: http://sigs.k8s.io/prow/README.md [prow tool]: https://sigs.k8s.io/prow/README.md
``` ```

6
github-management/README.md
View File

@ -103,13 +103,13 @@ intentions. [For more details please see community issue #1407](https://github.c
We have created a number of tools to help with the management of or Github We have created a number of tools to help with the management of or Github
repositories and organizations: repositories and organizations:
- [prow](http://sigs.k8s.io/prow/pkg): Prow is our system for handling - [prow](https://sigs.k8s.io/prow/pkg): Prow is our system for handling
GitHub events and commands for Kubernetes. It is comprised of a number of GitHub events and commands for Kubernetes. It is comprised of a number of
modules/plugins. A couple key ones for GitHub management are below, but a full modules/plugins. A couple key ones for GitHub management are below, but a full
list of commands is available [here](https://go.k8s.io/bot-commands) list of commands is available [here](https://go.k8s.io/bot-commands)
- [branchprotector](http://sigs.k8s.io/prow/cmd/branchprotector): - [branchprotector](https://sigs.k8s.io/prow/cmd/branchprotector):
enforce branch protection settings across an organization enforce branch protection settings across an organization
- [peribolos](http://sigs.k8s.io/prow/cmd/peribolos): Manage Github - [peribolos](https://sigs.k8s.io/prow/cmd/peribolos): Manage Github
organization and team membership based on a defined YAML configuration organization and team membership based on a defined YAML configuration
- [label_sync](https://git.k8s.io/test-infra/label_sync): Add, modify, delete, - [label_sync](https://git.k8s.io/test-infra/label_sync): Add, modify, delete,
and migrate labels across an entire organization based on a defined YAML and migrate labels across an entire organization based on a defined YAML

2
github-management/permissions.md
View File

@ -97,6 +97,6 @@ member in the organization.
[org permissions]: [org permissions]:
https://help.github.com/articles/permission-levels-for-an-organization/ https://help.github.com/articles/permission-levels-for-an-organization/
[OWNERS]: /contributors/guide/owners.md [OWNERS]: /contributors/guide/owners.md
[peribolos]: http://sigs.k8s.io/prow/cmd/peribolos [peribolos]: https://sigs.k8s.io/prow/cmd/peribolos
[repo permissions]: [repo permissions]:
https://help.github.com/articles/repository-permission-levels-for-an-organization/ https://help.github.com/articles/repository-permission-levels-for-an-organization/

2
github-management/setting-up-cla-check.md
View File

@ -61,7 +61,7 @@ instead of direct pushing that will never kick off a CLA check.
## Label automation ## Label automation
The label automation is done using the [CLA plugin in The label automation is done using the [CLA plugin in
prow](http://sigs.k8s.io/prow/pkg/plugins/cla). In order to turn on the prow](https://sigs.k8s.io/prow/pkg/plugins/cla). In order to turn on the
CLA labels on your repo, add it as appropriate within the CLA labels on your repo, add it as appropriate within the
[plugins.yaml](https://git.k8s.io/test-infra/config/prow/plugins.yaml), and add the cla [plugins.yaml](https://git.k8s.io/test-infra/config/prow/plugins.yaml), and add the cla
plugin to it. plugin to it.