annajung/documentation_example 3
Spring Rest Docs Demo
https://annajung.github.io
Kubernetes community content
Enhancements tracking repo for Kubernetes
Learning Go
Learning GraphQL
Kubernetes files for various *.k8s.io sites
Meta configuration for Kubernetes Github Org
Pull request review commentkubernetes/website
This label reflects the Windows major, minor, and build number that need to matc 1. Save this file to `runtimeClasses.yml`. It includes the appropriate `nodeSelector` for the Windows OS, architecture, and version. ```yaml-apiVersion: node.k8s.io/v1beta1+apiVersion: node.k8s.io/v1
pinging @sftim @kbhawkey @tengqm who can help answer this question
comment created time in a day
pull request commentkubernetes/website
Merge master into dev-1.20 to keep in sync
Thanks @eagleusb! /lgtm
will leave approval to someone else
comment created time in 2 days
push eventannajung/website
commit sha 580d1b31004e29e27a391e59c312fff13e2b7cdc
fix broken link: http://kubernetes.io/docs/home/contribute/page-templates/
commit sha f543b530fb53f44cf4585fc9134f24e95fec6d5b
ID Fix link emphasize
commit sha 839c4bcf90381936308b714974af4ff4696a2e8c
Update volume-snapshots.md
commit sha 3db8dcc4a629e6f7f84a04ac29d3a3e9affcc94c
update link
commit sha 429c78f8f62f1aab8371f74cbad46112703eae0b
update README-ko.md
commit sha 92fd3569b31c1443e020704be5af2a94ffe0de76
add v1.18 api ref to redirects
commit sha c732907fc870e43d0b2c21821dafb575b569208d
Update multiple-zones.md
commit sha 43c987054ef61c563ff22ea08746d3ff4603d19c
adjust table margin bottom
commit sha b22dae1712eb36afde1874f2fde3d844091a428d
README.md: Specify Hugo version Not all Linux distros or Operating Systems ship Hugo Extended version as default. If users try to run the website project without the extended version it will fail. Signed-off-by: Douglas Schilling Landgraf <[email protected]>
commit sha 407eb62fcf8b624fd984e944bb46fcfcd8b4b808
README.md: add troubleshooting session for hugo In case users run hugo (non extension version) we should have a quick link for helping new developers/users to solve the website build issue. Signed-off-by: Douglas Schilling Landgraf <[email protected]>
commit sha 52d52488f6209a2dcea1e67d2af7c3569fa9b6fe
cleanup docs owners
commit sha 2ac805485b8cc5db8ac97529c22e69af5895895a
rbac-ja
commit sha ee9961c59f7966f4be347e42e6ff347cc1d86463
Update content/ja/docs/reference/access-authn-authz/rbac.md OKです！ Co-authored-by: inductor(Kohei) <[email protected]>
commit sha 9edf2eaf198d09bd17b1288cf9a40ffb99bf4503
Modified verb "コントロール" into "制御"
commit sha 735410f17b6bf8445c6f7d1978adeeadd8a4ded4
Only load copy-and-paste helper on pages that use it This change helps improve load times for key non-documentation pages such as https://kubernetes.io/
commit sha 68a12f7620e0b97f0e7cf7652655f2d2f3d15f7e
Modified some points Thanks sftim. I am working on for other points too.
commit sha 4065897e2027248cfc74b09c4c33c53dc048300b
Update content/ja/docs/reference/access-authn-authz/rbac.md Modified glossaryreference from "API group" to "api-group" for future localization Co-authored-by: Tim Bannister <[email protected]>
commit sha 92017b045f0044fffaa9aec1ee5fa3ea28d9e71d
Update content/ja/docs/reference/access-authn-authz/rbac.md Corrected Original plural to localize. Co-authored-by: Tim Bannister <[email protected]>
commit sha 1dac786c118035d9c98041aed44aa6ce51c5271b
Update content/ja/docs/reference/access-authn-authz/rbac.md Modified Original plural to localize. Co-authored-by: Tim Bannister <[email protected]>
commit sha 345a7f80a8a9bda95d9d0e43df5df31f343a4621
Update content/ja/docs/reference/access-authn-authz/rbac.md I'll take it this because there is no examples or mentions deny in "deny" format before/after this line. Co-authored-by: Tim Bannister <[email protected]>
push time in 2 days
Pull request review commentkubernetes/enhancements
Update issue template to divide into alpha/beta/stable
- Discussion Link: <!-- link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation --> - Primary contact (assignee): - Responsible SIGs:-- Enhancement target (which target equals to which milestone):- - Alpha release target (x.y)- - Beta release target (x.y)- - Stable release target (x.y)-- Documentation PR: <!-- link to kubernetes/website PR -->- - Alpha:- - Beta:- - Stable:+- [ ] Alpha+ - [ ] Release Target (x.y): <!-- target equals to which milestone -->+ - [ ] KEP (`k/enhancements`) update PR(s):+ - [ ] Code (`k/k`) update PR(s):+ - [ ] Docs (`k/website`) update PR(s):+- [ ] Beta
I agree that it's cleaner that way, but I also think that having it in the issue template serves as a reminder to the Enhancement owners that they eventually should go back and add beta/stable information in the description. No strong opinions either way though.
comment created time in 2 days
Pull request review commentkubernetes/enhancements
Update issue template to divide into alpha/beta/stable
- Discussion Link: <!-- link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation --> - Primary contact (assignee): - Responsible SIGs:-- Enhancement target (which target equals to which milestone):
Thanks for the feedback, it's been updated! :D
comment created time in 2 days
push eventannajung/enhancements
commit sha 008c5c24a507e9978f663c1a78e0d6b0941e620e
Update issue template to divide into alpha/beta/stable
push time in 2 days
issue commentkubernetes/sig-release
Yes, I'll wait until after the sig docs planning today
comment created time in 3 days
issue commentkubernetes/sig-release
Also, commenting on "Leverage Implemented field from enhancements tracking sheet to determine if the corresponding docs PR can be merged/not", I think we actually want to make sure k/k prs are merged in and the enhancement team is one that's responsible for making sure the enhancement is not tracked if it's not in the "implementable" state.
So, I'm not sure what the action item here is. But, during the sig docs quarterly planning meeting, I'm planning on discussing how to automate the k/k pr "look up" for docs in an automated way. Regardless, I think this should be a separate issue as it's not an easy change.
comment created time in 3 days
issue commentkubernetes/sig-release
@savitharaghunathan We can mark "Templates for deadline communication - PR in progress" as done :)
I think we can also mark " Look into improving the current process of tracking enhancement docs with help from the enhancement team..." as done. I've been working with Kirsten during the release to make the process smoother which involved adding docs placeholder deadline for the enhancement team and adding docs into the enhancement issue template (https://github.com/kubernetes/enhancements/pull/2016).
comment created time in 3 days
pull request commentkubernetes/website
/milestone 1.20 /assign @SomtochiAma /sig instrumentation
comment created time in 3 days
pull request commentkubeflow/website
Fix broken links for community page topics
@googlebot I signed it
comment created time in 3 days
PR opened kubeflow/website
- Fix broken links for the WG AutoML and WG Training on the community page
- Clean up slack URL for the working group for consistent URL across all slack urls
pr created time in 3 days
push eventannajung/website-1
commit sha 1f8976a2836e92cea5d02c27fb5f59ab0988ddce
Fix broken links for community page topics
push time in 3 days
fork annajung/community-1
Information about the Kubeflow community including proposals and governance information.
fork in 3 days
PR opened kubernetes/enhancements
Modify the issue template to divide up into alpha, beta, and stable to track resource changes based on the release. (This is a follow up on https://github.com/kubernetes/enhancements/pull/2016 based on https://github.com/kubernetes/enhancements/pull/2016#issuecomment-713118605)
/hold for feedback from the Enhancement team
cc @justaugustus @mrbobbytables @kikisdeliveryservice
pr created time in 3 days
push eventannajung/enhancements
commit sha 253f1e5bdd121872d2d0f7020a5ac0365b229e30
Memory Manager KEP Signed-off-by: Byonggon Chun <[email protected]>
commit sha 9745c391dcb8abe73227e38da8745923d4ac9e88
fix type & add authors Signed-off-by: Byonggon Chun <[email protected]>
commit sha 8414610d607734fc73e2fed24ec627f7f6b27f99
KEP: hardened exec requests
commit sha 9a2239fde76535a80b83a47d530cd0fbc8af69c0
Fix metadata
commit sha 05b3f56f627d343dd1050fa69dd131301b4b3458
KEP-1933: Defend Against Credential Logging in Prow
commit sha e3db0ae9cc9373e083826bce9c7e26e806e65b83
CodeQL now has Go support. Investigate as an alternative.
commit sha 24da61294c9b57698ebae8655f8197c264879109
Improve title clarity. Prow as testing is incidental.
commit sha 5a030c9c725203ecc3df6ccad205d0131ee16c6d
Remove not-yet-existent sig-security
commit sha c528a21e1ba7c3c11d28fa40bb0586413180bad0
Remove Inapplicable Monitoring Requirements
commit sha ee235330dd8c101cfa540d6f1cc22024d8e4a862
Respond to comments. * Explicitly note empty sections are not applicable to test-only KEP. * Include Drawbacks. Future commit to remove redundancy.
commit sha 40670f6d181fe781f514313ee7834e79f6d39a96
KEP-1972: kubelet exec probe timeouts Signed-off-by: Andrew Sy Kim <[email protected]>
commit sha ebd059ca99a672228f75d0c70140ce2bc1cd8d4e
sidecar: Remove old phrase in non-goals This was requested by Sergey here: https://github.com/kubernetes/enhancements/pull/1913#discussion_r482207970 Signed-off-by: Rodrigo Campos <[email protected]>
commit sha c8469da288f3bf8914bea815a1e2935957471fd7
sidecar: Clarify all sidecars start in parallel As requested by Sergey: https://github.com/kubernetes/enhancements/pull/1913#discussion_r482210989 Signed-off-by: Rodrigo Campos <[email protected]>
commit sha b71de799870fa1f2de321b19a74a571a3fca6f27
sidecar: Don't modify the pod phase One decision to revisit was to see if really wanted to change the pod phase. It was clearly agreed here that we won't: https://github.com/kubernetes/enhancements/pull/1913#discussion_r482212580 This commit just removes the section to discuss that (it is already agreed) and updates the KEP to reflect that. Signed-off-by: Rodrigo Campos <[email protected]>
commit sha 693c4c21711928a1d7329c589bff3e807df2f766
sidecar: Don't send preStop hook twice This was added due to a comment from Istio long ago[1], but they don't need this anymore[2]. Furthermore, our use cases at Kinvolk also work just fine without this. [1]: https://github.com/kubernetes/community/pull/2148#issuecomment-422429820 [2]: https://github.com/kubernetes/enhancements/pull/1913#discussion_r464498249 Signed-off-by: Rodrigo Campos <[email protected]>
commit sha 2badf865c40444edbd651dbe6c164d3c68dff583
sidecar: Address handling of the pod=nil case Signed-off-by: Rodrigo Campos <[email protected]>
commit sha 95c588eb96756b29a4a2987d483c1d76e405efa3
sidecar: Move some sections to caveats This commit just move some section to caveats with a clarification on why it seems enough to do this on each. Signed-off-by: Rodrigo Campos <[email protected]>
commit sha 9a6a36751bbb442690e9356b8660462036de68b3
sidecar: Remove addressed concerns These concerns have been discussed: * "No container type standard". As pointed, this was already discussed and agreed in the past. * "Is this change really worth doing?". It seems it is, given the community response and the problems stated there can only be solved at the Kubernetes layer * "Why this design seems extensible?". Didn't present any major concerns and it does seem extensible. * "Sidecar containers won't be available during initContainers phase". We had a VC with Sergey and Joseph and agreed that it is out of scope for this KEP. Signed-off-by: Rodrigo Campos <[email protected]>
commit sha b6214c993494450e556e0304b1defacf869a44fa
sidecar: Document increased time to kill a pod in the worst case As discussed in SIG-node on 08.09.2020 and suggested by Sergey, we can just document the caveat that it might take 4s longer to kill a pod with sidecar containers. This is very simple, even simpler than the alternatives listed. Signed-off-by: Rodrigo Campos <[email protected]>
commit sha 2a17744bd4b6e2aeef68b77aa2a5aeff440e0797
sidecar: Address concern about kill time 3x longer Signed-off-by: Rodrigo Campos <[email protected]>
push time in 3 days
PR opened kubernetes/test-infra
Adding hashtag (#) to the invalid commit message plugin which already handles both @ and # in the PR title
pr created time in 3 days
push eventannajung/test-infra
commit sha a351777679c7501d7e2d4df52bcde25018cfbea6
[CAPZ] ADD periodic to run coverage report
commit sha a88c0ef4372bf3c9fbde3ea5ee001d892090281a
label_sync: rename triage/support to kind/support https://github.com/kubernetes/enhancements/blob/c7d895dbec5304345cb797113fdefd7be5761720/keps/sig-contributor-experience/1553-issue-triage/README.md#rename-the-triagesupport-label Co-authored-by: Stephen Augustus <[email protected]>
commit sha 3d7d537a3ebc66b118857a79e6d50b657878e349
prow: allow org members to add triage/accepted label Ref: https://github.com/kubernetes/enhancements/blob/c7d895dbec5304345cb797113fdefd7be5761720/keps/sig-contributor-experience/1553-issue-triage/README.md#needs-triage-and-triageaccepted-labels Co-authored-by: Stephen Augustus <[email protected]>
commit sha d8166efa22df42f6407c0e223700c46d3db47d57
config/prow: apply needs-triage to all issues in k/k Ref: https://github.com/kubernetes/enhancements/blob/c7d895dbec5304345cb797113fdefd7be5761720/keps/sig-contributor-experience/1553-issue-triage/README.md#needs-triage-and-triageaccepted-labels Co-authored-by: Stephen Augustus <[email protected]>
commit sha a2e481c125220f1808c00296f3ec55fc30e1adb1
Updated email for sig node release blocking jobs Signed-off-by: alejandrox1 <[email protected]>
commit sha f54cd1bf578d1c414d8df8c4f44856bd5d17c669
Deck: support bucket/folder whitelist
commit sha b785af906b2228018544d7a55938e05baeafd852
minimize ValidatePath set insertions
commit sha dff5e2ea3283c1a0e7f5f8074f0059eb72903d7e
Adding custom HTTP status code for path validation errors
commit sha 9bfd438f4a706315d7551ea832d19d6ca98dd611
fix(kubeflow): don't protect branches created by editing on GitHub UI
commit sha 8a2e0ff46bf00b6f5b5aaf5d282ef3e03202c657
post-test-infra-push-prow: run when GCSWeb changes The job publishes the GCSWeb image, so it needs to run when the source changes. Signed-off-by: Steve Kuznetsov <[email protected]>
commit sha bbe98c1efe59e3e3e85726026133f1e24992c9a0
Pushing bucket validation into storage-access layers. Some refactoring in StorageArtifactFetcher and guarding access to blobStorageBucket.
commit sha 968caee6472019c9487e13ca31ef5abada54518e
add a content-type header even when encoding is missing Signed-off-by: Nikolaos Moraitis <[email protected]>
commit sha c66a02a118ac483c3df778c825696717a772d062
Merge pull request #19337 from Bobgy/patch-6 fix(kubeflow): don't protect branches created by editing on GitHub UI
commit sha 41397747dd3cedf13d4af084d23e32c5cefcbc54
Merge pull request #19357 from droslean/fix-content-type [gcsweb] add a content-type header even when encoding is missing
commit sha 3ba54bbf9b3dc473a61f05f6a0d47e681b1853a1
Clean up gke kubetest provider
commit sha e3dabd2890c8127a31404c3c075b834847113729
Merge pull request #18945 from cpanato/add-periodic-coverage [CAPZ] ADD periodic to run coverage report
commit sha b08b9c59e07ba5c83677186300fb3afdea984812
Fix capi test image
commit sha 997ea8953d9756fedd4f6a0cd5c6b56d65cb0491
Merge pull request #19363 from benmoss/capi-external-links Fix capi test image
commit sha 9adb22a65b716350651bd13363bcc009f292daa5
Update prow to v20200924-4bb1aa1ffa, and other images as necessary.
commit sha 9d8ab99aabf76f00432689bcae10836add0f6726
Merge pull request #19351 from k8s-ci-robot/autobump Update prow to v20200924-4bb1aa1ffa, and other images as necessary.
push time in 3 days
Pull request review commentkubernetes/sig-release
feat(docs) add rebase method for periodically master sync
git commit -m "Merge master into dev-[future release] to keep in sync" git push origin merged-master-dev-[future release] ``` -Submit a PR against upstream `dev-[future release]` from your fork's branch `merged-master-dev-[future release]`. e.g., [merge master into future release](https://github.com/kubernetes/website/pull/16225).- You may need to fix conflicts manually. If somebody has improved a page on `master`, and at the same time it has been updated in the dev branch for the next release, we may need to figure out how to make those changes work together. If something comes up which isn't obvious, you can always abort the merge and reach out to SIG Docs for help. When you have completed resolving the differences manually, run `git merge --continue` to complete the merge. Then carry on from step 5. -⚠️ **Ensure the PR is passing tests on GitHub**.+> Rebase Method
Any input on preference on merging vs rebasing would really help! Maybe we can add the reasoning to docs as well.
I also thought about why we merge instead of rebasing and clarifying this will help future shadows who might have the same questions.
comment created time in 3 days
pull request commentkubernetes/website
@sftim @kbhawkey, PTAL again when you can, looking for a review/ lgtm from Sig Docs
comment created time in 4 days
pull request commentkubernetes/website
Updating doc for setHostnameAsFQDN feature to beta in v1.20
/lgtm /approve
comment created time in 4 days
Pull request review commentkubernetes/website
add documentation for system:monitoring rbac policy
This is commonly used by add-on API servers for unified authentication and autho <td>None</td> <td>Allows access to the resources required by most <a href="/docs/concepts/storage/persistent-volumes/#provisioner">dynamic volume provisioners</a>.</td> </tr>-<tbody>+<tr>+<td><b>system:monitoring</b></td>+<td><b>system:monitoring</b> group</td>
Hi @kbhawkey, using backticks resulted in the following (https://github.com/kubernetes/website/pull/22715#issuecomment-705832853) so I suggested to change to <tt>. It doesn't seem to be deprecated as the page renders as expected (https://5f7f97dbc52f3c00071d9bee--kubernetes-io-vnext-staging.netlify.app/docs/reference/access-authn-authz/rbac/). PTAL when you can, thank you!
@logicalhan pinging to review Karen's suggestions! :D
comment created time in 4 days
pull request commentkubernetes/website
The Memory Manager official documentation
/hold until k/k PR (https://github.com/kubernetes/kubernetes/pull/95479) is merged
comment created time in 5 days
pull request commentkubernetes/website
The Memory Manager official documentation
/sig node
comment created time in 5 days
pull request commentkubernetes/website
The Memory Manager official documentation
/milestone 1.20 /assign @eagleusb @annajung
comment created time in 5 days
issue commentkubernetes/enhancements
Add downward API support for hugepages
Hello @derekwaynecarr 👋 , 1.20 Docs lead here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
comment created time in 5 days
issue commentkubernetes/enhancements
Hello @bobbypage 👋 , 1.20 Docs lead here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
comment created time in 5 days
issue commentkubernetes/enhancements
Support to size memory backed volumes
Hello @derekwaynecarr 👋 , 1.20 Docs lead here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
comment created time in 5 days
issue commentkubernetes/enhancements
Defend against logging secrets via static analysis
Hello @PurelyApplied 👋 , 1.20 Docs lead here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
comment created time in 5 days
issue commentkubernetes/enhancements
Kubelet Feature: Disable AcceleratorUsage Metrics
Hello @RenaudWasTaken 👋 , 1.20 Docs lead here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
comment created time in 5 days
Pull request review commentkubernetes/sig-release
+# Release Timeline+For each release, the schedule with deliverables is added to the release directory. This section talks about specific Docs Lead deliverables for each milestone in the release timeline.++- [Early Steps (Weeks 1-2)](#early-steps-weeks-1-2)+ - [Connect with the release team through Slack and Google Groups](#connect-with-the-release-team-through-slack-and-google-groups)+ - [Read the release timeline](#read-the-release-timeline)+ - [Introduce yourself](#introduce-yourself)+ - [Attend meetings](#attend-meetings)+ - [Read up on the release team](#read-up-on-the-release-team)+ - [Select Shadows](#select-shadows)+ - [Contact volunteers](#contact-volunteers)+ - [Meet with Shadows](#meet-with-shadows)+ - [Ensure access is set up](#ensure-access-is-set-up)+ - [Update the website configuration ahead of the release](#update-the-website-configuration-ahead-of-the-release)+- [Middle Steps (Weeks 3-8)](#middle-steps-weeks-3-8)+ - [Track PRs](#track-prs)+ - [Reach out to Enhancement Owners](#reach-out-to-enhancement-owners)+ - [Before the Open placeholder PR Deadline](#before-the-open-placeholder-pr-deadline)+ - [Before the PRs Ready for Review Deadline](#before-the-prs-ready-for-review-deadline)+ - [Before the PRs Ready to Merge Deadline](#before-the-prs-ready-to-merge-deadline)+ - [Reach out to release notes team](#reach-out-to-release-notes-team)+ - [Maintain the current and upcoming `dev` branch](#maintain-the-current-and-upcoming-dev-branch)+ - [Periodically merge `master` into `dev-[future release]`](#-periodically-merge-master-into-dev-future-release)+ - [Monitor PRs](#monitor-prs)+ - [Enforce deadlines](#enforce-deadlines)+ - [Communicate major deadlines](#communicate-major-deadlines)+ - [Review PRs](#review-prs)+ - [Style Guide Checklist (High to Low Level)](#style-guide-checklist-high-to-low-level)+ - [Nominate a Docs Lead for the Next Release](#nominate-a-docs-lead-for-the-next-release)+- [Late Steps (Weeks 9-11) - Prep for the release](#late-steps-weeks-9-11---prep-for-the-release)+ - [Generate the reference documentation](#generate-the-reference-documentation)+ - [Update minor version on API index page](#update-minor-version-on-api-index-page)+ - [Touch base with SIG Cluster Lifecycle (kubeadm)](#touch-base-with-sig-cluster-lifecycle-kubeadm)+ - [Update the `config.toml`s for the past four releases](#update-the-configtomls-for-the-past-four-releases)+ - [Deprecate links](#deprecate-links)+- [Release Week (Week 12)](#release-week-week-12)+ - [Create the release branch](#create-the-release-branch)+ - [Update Netlify](#update-netlify)+ - [Freeze Kubernetes website](#freeze-kubernetes-website)+ - [Inform localization teams](#inform-localization-teams)+ - [Review milestones](#review-milestones)+- [Release Day](#release-day)+ - [Merge `master`](#merge-master)+ - [Create release with tag](#create-release-with-tag)+ - [Unfreeze](#unfreeze)+ - [Close the [future release] milestone](#close-the-future-release-milestone)+- [Post Release Verification, Cleanup, and Handoff](#post-release-verification-cleanup-and-handoff)+ - [Update Release Notes Changelog](#update-release-notes-changelog)+ - [Review Docs Process and Update Documentation](#review-docs-process-and-update-documentation)+ - [Hold a docs-only burn down](#hold-a-docs-only-burn-down)+- [Prepare the Next Docs Lead for Success](#prepare-the-next-docs-lead-for-success)+ - [Create branches](#create-branches)+ - [Create milestone](#create-milestone)+ - [Update Netlify](#update-netlify)+ - [Update Slack](#update-slack)+ - [Reassign issues](#reassign-issues)+- [Celebrate](#celebrate-)+++## Early Steps (Weeks 1-2)+These steps take approximately one hour to complete, and should be completed immediately.++### Connect with the release team through Slack and Google Groups++- Join the Kubernetes [#sig-release](https://kubernetes.slack.com/messages/sig-release) Slack channel. Introduce yourself as the Docs Lead for the [future release].++- Send a Slack direct message to the [future release] lead to introduce yourself.++- ⚠️ Join these Google groups:+ - [kubernetes-sig-release](https://groups.google.com/forum/#!forum/kubernetes-sig-release)+ - [kubernetes-sig-docs](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)+ - [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev)+ - [kubernetes-release-team](https://groups.google.com/a/kubernetes.io/g/release-team)+ - ⚠️ List of members for this group is managed in git. Please create a PR against `kuberenetes/sig-release` repo to include your email under `release-team` group in [`sig-release/group.yaml`](https://github.com/kubernetes/k8s.io/blob/master/groups/sig-release/groups.yaml) + - [kubernetes-release-team-shadows](https://groups.google.com/a/kubernetes.io/g/release-team-shadows)+ - ⚠️ List of members for this group is managed in git. Please create a PR against `kuberenetes/sig-release` repo to include your email under `release-team-shadows` group in [`sig-release/group.yaml`](https://github.com/kubernetes/k8s.io/blob/master/groups/sig-release/groups.yaml)++- Make sure you're included in the "official" release team file, e.g: [release 1.14](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.14/release_team.md). If not submit a PR and add yourself.++Early in the release cycle, the Release Manager opens an enhancement tracking spreadsheet, e.g: [the 1.14 release spreadsheet](https://docs.google.com/spreadsheets/d/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48nsedit#gid=0). Later in the release this spreadsheet will contain important information for docs:++- Which enhancements we'll be tracking for this release+- Feature owners (and their GitHub IDs)+- Links to docs PRs opened for each enhancement++### Read the release timeline++Read the release timeline and **make sure the timeline includes deadlines for documentation work**, e.g: [1.14 timeline](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.14#timeline):++- Docs deadline - Open placeholder PRs (~3.5 weeks before release)+- Docs deadline - PRs ready for review (~2 weeks before release)+- Docs complete - All PRs reviewed and ready to merge (~1 week before release)++If these deadlines aren't listed in the release timeline, request that the Release Lead add them.++### Introduce yourself++Introduce yourself to the current localization owners to sync up early on strategy (needs coordination for main release). e.g: [Formalize docs release strategy with the different localization owners](https://github.com/kubernetes/website/issues/12396).++### Attend meetings++⚠️ Attend the release team meeting outlined in the current release. If you cannot attend, a Shadow needs to attend in your place.++### Read up on the release team++Read this to learn more about the entire [release team and process](https://github.com/kubernetes/sig-release/tree/master/release-team)++### Select Shadows++You will be provided with survey results from people interested working on the release team. If you do not have the results, contact the release lead for more information.++After vetting the volunteers for their roles, role leads should make a final decision on selected shadows with the incoming Release Team Lead. In the past the SIG Docs release team has been between 3-6 members.++⚠️ Beyond meeting the basic requirements and time commitments, a good Shadow is someone who is active in SIG-Docs. Selection priority should go to previous shadows who want to eventually lead a SIG-Docs release. Other than those few guidelines, use your best judgement!++[Link for additional information on shadows](https://github.com/kubernetes/sig-release/blob/master/release-team/release-team-selection.md#shadows)++### Contact volunteers++Send a Slack message to those that you select, e.g:++> Hey, you're officially on the SIG Docs 1.14 release team as a shadow! Let me know if there's any issues with being a shadow (as far as timing / availability / etc) and feel free to introduce yourself!+>+> Let me start: [General Introduction about your name, workplace, k8s community involvement, timezone etc]+>+>Ok, on to the business...+>+>We are an inclusive group so if there’s something you’re concerned about, or don’t understand, don’t worry and just ask!+>+> First off, check out the release team on-boarding guide: https://github.com/kubernetes/sig-release/blob/master/release-team/release-team-onboarding.md+>+>Make sure you join the following Slack channels: #sig-docs, #sig-release, #release-docs+You'll then want to join these mailing lists if you haven't already:+>- https://groups.google.com/forum/#!forum/kubernetes-sig-release+>- https://groups.google.com/forum/#!forum/kubernetes-sig-docs+>- https://groups.google.com/forum/#!forum/kubernetes-dev+>+>Access to google docs and calendar invites are often based on these mailing lists, so it's a good idea to subscribe.+>+>When it comes to contributing and reviewing PRs, you should check out the docs style guide: https://kubernetes.io/docs/contribute/style/style-guide/+>+>We'll go over this in the meeting, but you may also want to take a quick look at the 1.14 release readme. https://github.com/kubernetes/sig-release/blob/master/releases/release-1.14/README.md+>+>Lastly, I'd love to jump on a call to go over the release process with everybody, describe what we'll be doing, and answer any questions. Below is a poll to see what time works best on Friday (if any). As we near the end of the release cycle I will add a regular weekly check-in.+>+>Please select your preferred time(s) Friday: https://doodle.com/<link-removed>+++⚠️ Please coordinate with Emeritus Adviser for the release before taking this step.+Send a Slack message to those that you didn't select, e.g:++> Hey, I'm Jim Angel (Docs Lead for SIG Docs). Thanks for your interest in the SIG Docs 1.14 release team!+>+> The release team for sig-doc shadows has no additional availability, but please stick around help out with some of our other sigs (including sig-docs)!+>+> How can you help?+> - Attend the sig release meetings (07 30 AM PST Bi-weekly on Tuesdays - see #sig-release for more info).+> - SIG-DOCs is always looking for new contributors, please go introduce yourself and we're happy to help! As a bonus, you will be preferred during the next release cycle as opposed to someone not involved with sig-docs.+ - Slack is full of other great SIGs that could always use your help!+>+> I am also a resource to reach out to if you have any community questions (there's also #sig-contribex). I started out as a volunteer and now I am part of many Kubernetes sigs and teams.+>+> Thanks again for your interest and time!+>+> Jim Angel+++### Meet with Shadows++Find .5-1 hour of time to meet with shadows and explain the release process. Walk through this entire document and review the flow with them. It helps to set expectations that the mantra is "hurry up and wait" but then it gets very hectic at the end. If you have the ability to, please record the meeting and share it with your Shadows for future review.++1. Add contacts to the shadows release docs, e.g: [https://bit.ly/k8s114-contacts](https://docs.google.com/spreadsheets/d/1BiGSLuCqjglQS1bJvpKk6rKFMciebPkUndzgDRnJsns/edit?ts=5c3bd42a#gid=0)++### Ensure access is set up++1. Make sure all shadows have edit access to the enhancement spreadsheet.++1. As a lead, make sure you are part of the [milestone-maintainers](https://github.com/orgs/kubernetes/teams/milestone-maintainers) and [sig-docs-en-owners](https://github.com/orgs/kubernetes/teams/sig-docs-en-owners).++1. You need push access to the Kubernetes website repo (contact a SIG Docs chair if you don't have it)++ ⚠️ (**This should be done by the Docs Lead**) Open the [integration branch] by creating a pull request against `master` referencing the `dev-[future release]` branch e.g., the [Release 1.14](https://github.com/kubernetes/website/pull/13174) PR uses the branch `dev-1.14`.++ This release pull request (also known as the [integration branch]) serves as the base for individual, component enhancement PRs of the release. A [integration branch] lets you bundle and merge multiple PRs simultaneously.++ ⚠️ Add the label `do-not-merge/hold` to the PR.++1. First PR in `dev-[future release]`: Update config.toml to show `[future release]` as the current version and add the `[future release]` entry to the drop-down, e.g: [config.toml diff](https://github.com/kubernetes/website/pull/20847)++ The intent is that your new branch should be showing as the current version IN the new branch...++### Update the website configuration ahead of the release++Update the main `config.toml` based on the version on the `master` branch. Open a PR for these changes against the `dev-[future release]` branch (which should already exist - this is a good check!)++```shell+# Step 1+# Do this on a fresh local clone OF YOUR FORK+# It's OK to use SSH for the git URL if you know how to do that+git clone https://github.com/yourGitHubUsername/website.git kubernetes-website+cd kubernetes-website+# Step 2+# Add the upstream repo as a remote+git remote add upstream https://github.com/kubernetes/website.git+git checkout --track master+git checkout -b config-toml-1.14 # change for the release you're making+# Step 3+# Edit config.toml to make the changes described above+# save your changes+git add config.toml+git commit -m "Updated config.toml for 1.14 release"+# Step 4+# Check things look right+git status+git remote -v+# Step 5+# Push this new branch to your fork+git push origin config-toml-1.14+```++Now create a pull request that targets the next release (here: `dev-1.14`) **not** `master`.+++## Middle Steps (Weeks 3-8)+The middle weeks of the launch are where the Docs Lead and Docs Lead Shadows track and review incoming PRs.++### Track PRs++Track PRs based on the enhancement (KEP) spreadsheet.++Keep the enhancement tracking spreadsheet up to date with review progress and merge status for each documentation PR. For example: [Kubernetes Enhancements OSS tracking board (1.14 release)](https://docs.google.com/spreadsheets/d/116X6E-lmDJG5UZPlqDAFw8hN9vS6SNY4qRNZ9fKtsMU/edit#gid=0)++⚠️ Assign the enhancements evenly across your Shadows after the enhancement freeze. Assigning shadows before the+ enhancement freeze will cause unexpected behavior in the tracking spreadsheet due to frequent updates to dynamic data.+ (Tip: When assigning enhancements, try grouping enhancement owners and/or by SIGs)+ - You and your Shadows will be responsible for tracking whether the enhancement:+ - **has docs:** Actively has docs in place on Kubernetes website or in flight+ - **needs docs:** Actively needs docs to support the enhancement in the [future-release]+ - **unknown:** After reviewing the KEP, it is unclear if this needs docs or not+ - **not required:** The KEP doesn't change anything that requires reflection in Kubernetes website+ - You and your Shadows will also be responsible for marking whether the docs are:+ - **Complete (Merged):** PR on the dev-[future-release] is done and merged+ - **No PR:** No PR is open (helpful for dead line tracking)+ - **Late:** No PR is open AND it's passed the deadline+ - **Draft (PR):** PR is open but content isn't ready for review+ - **Ready for Review (PR):** PR is open but content IS ready for review+- ⚠️ Make sure that every docs PRs for the release have the correct base and set the correct Milestone. For example, enhancement PRs for version 1.14 need abase branch of `dev-1.14` and the Milestone set to `1.14`.++The spreadsheet can be used to track the current health of the docs for release. For example:++++On the "Enhancement Stats" tab, a table was created to track the Doc Stats and then based on their category, in the other tab, assign a status "Green / Yellow / Red."++This is very helpful for weekly reports and managing deadlines++### Reach out to Enhancement Owners++#### Before the Open placeholder PR Deadline+After the Enhancement Freeze, reach out to all tracked enhancements to see if new docs or modification to existing docs+are required, e.g:++> Hello < tag enhancement owner(s) > :wave:, < future-release > Docs < Shadow/Lead > here.+>+> Does this enhancement work planned for < future-release > require any new docs or modification to existing docs?+>+> If so, please follows the steps [here](https://kubernetes.io/docs/contribute/new-content/new-features/#open-a-placeholder-pr)+> to open a PR against `k/website` repo. This PR can be just a placeholder at this time and must be created before < docs placeholder deadline >
Thanks for the feedback Rey! That's a great idea, it's been updated! :D
comment created time in 7 days
push eventannajung/sig-release
commit sha bf188d2543c7c9d98107cf5105b040ec9ea3f16a
Add branch specification to the template
push time in 7 days
issue closedkubeflow/community
https://www.kubeflow.org/docs/about/community/#slack-community-and-channels link for "invitation to our Slack workspace" result in a server error message from slack
Can someone share a valid link to join the kubeflow slack workspace?
closed time in 8 days
annajung
issue commentkubeflow/community
looks like it was a problem with the slack system! (https://status.slack.com/) closing this issue as no further action is required!
comment created time in 8 days
issue openedkubeflow/community
https://www.kubeflow.org/docs/about/community/#slack-community-and-channels link for "invitation to our Slack workspace" result in a server error message from slack
Can someone share a valid link to join the kubeflow slack workspace?
created time in 8 days
issue commentkubernetes/enhancements
Support 3rd party device monitoring plugins
Hello @RenaudWasTaken , 1.20 Docs lead here.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th
Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
comment created time in 8 days
pull request commentkubernetes/website
Hey @danwinship can you change the base to dev-1.20 instead of master?
comment created time in 9 days
pull request commentkubernetes/website
/milestone 1.20 /assign @annajung @kcmartin /sig network
enhancement: https://github.com/kubernetes/enhancements/issues/614 k/k (merged): https://github.com/kubernetes/kubernetes/pull/95566
comment created time in 9 days
PR opened kubernetes/sig-release
<!-- Thanks for sending a pull request! Here are some tips for you:
- If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
- Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
- If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
- If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->
What type of PR is this:
/kind documentation /kind cleanup
<!-- Add one of the following kinds: /kind cleanup /kind documentation /kind feature /kind design -->
What this PR does / why we need it:
- Add templates that can be used to communicate docs deadline to enhancement/docs PR owners (Please look at this commit to see which content were changed: https://github.com/kubernetes/sig-release/commit/bf3ac59d23a68cc0c858851aae2a20ce7ce6deef)
- Extract out the release timeline section into its own file to help with readability (removes used of h5 which is smaller than a regular text!)
Which issue(s) this PR fixes:
None
<!--
*Automatically closes linked issue when PR is merged.
Usage: Fixes #<issue number>, or Fixes (paste link of issue).
Fixes # or None -->
Special notes for your reviewer:
/assign @savitharaghunathan @jimangel
pr created time in 10 days
push eventannajung/sig-release
commit sha 3684e8efc960da4f2349e3e684f97adc641d90ed
Separate release timeline into its own doc for readability
push time in 10 days
push eventannajung/sig-release
commit sha 9f43ab7cd9b83c84dd45d1c2baf5b68ebb78b1c1
Separate release timeline into its own doc for readability
push time in 10 days
push eventannajung/sig-release
commit sha 12b38056385665969be218139cd7a049bc6252af
Separate release timeline into its own doc for readability
push time in 10 days
push eventannajung/sig-release
commit sha 563285a0a35714dc0a754cb916d09944e33dcd98
Separate release timeline into its own doc for readability
push time in 10 days
push eventannajung/sig-release
commit sha bf3ac59d23a68cc0c858851aae2a20ce7ce6deef
Add template for reaching out to PR owners for doc deadlines
push time in 10 days
push eventannajung/sig-release
commit sha 4a7f128ae15e46653b1f2a99732167a5ee92a348
Add template for reaching out to PR owners for doc deadlines
push time in 10 days
push eventannajung/sig-release
commit sha 8519558506abbc838312de41bfb4cd9f0b3db7d9
Cleanup OWNER_ALIASES Signed-off-by: Jeremy Rickard <[email protected]>
commit sha ab35e513624f07a4c249513932265c83d6f3d4ac
Merge pull request #1268 from annajung/master Add access details and clean up wrong url in docs role handbook
commit sha b2ff46dfdfcb7de8f1a6b9f4837bc068793a0400
Merge pull request #1267 from jeremyrickard/cleanup-owner-alias Cleanup OWNER_ALIASES
commit sha 226cde8f49a6fc6c9adec09ec189eb94157270c2
Release Notes draft for k/k v1.20.0-alpha.1 Signed-off-by: James Laverack <[email protected]>
commit sha bf82b9dfe4b60254cd7c5c56ef22916fd1a0927c
Merge pull request #1269 from JamesLaverack/release-notes-draft-v1.20.0-alpha.1 Update release notes draft to version v1.20.0-alpha.1
commit sha f2af1a252614c228ed52fc2931d06a150ca2ba53
Update onboarding issue and RT Lead Handbook for Inclusive Speaker Orientation Signed-off-by: Jeremy Rickard <[email protected]>
commit sha 05ca7d42ef1a62796786e1130327b22556ad81f7
Release Notes draft for k/k v1.20.0-alpha.1 Signed-off-by: Celeste Horgan <[email protected]>
commit sha 6975bc05d7514ef6aae3a62cb6dc44ab96dc6334
Merge pull request #1273 from celestehorgan/release-notes-draft-v1.20.0-alpha.1 Update release notes draft to version v1.20.0-alpha.1
commit sha f3578d5fde8e431e604de90095beac0fdbd5ba3e
Add exceptions for the 1.19 release cycle Signed-off-by: Nabarun Pal <[email protected]>
commit sha db606943bb342c1ab55cbc4b7809a6e7cb6ebd6d
Merge pull request #1275 from palnabarun/retro-add-1-19-exceptions Add exceptions for the 1.19 release cycle
commit sha c89b433b7909a39d41e0856d2108b8465e8b8f2b
Merge pull request #1270 from jeremyrickard/add-cncf-unconscious-bias-requirement Update onboarding issue and RT Lead Handbook for Inclusive Speaker Orientation
commit sha cc77e41118a71bab277ba9376ca589ae55620dec
OWNERS_ALIASES: Add xmudrii to release-engineering-approvers
commit sha b8339c5e13ce2a8f820bf3b323440b65bdb4cd72
Merge pull request #1276 from xmudrii/update-owners OWNERS_ALIASES: Add xmudrii to release-engineering-approvers
commit sha d9bd8efb897ea1bdb7e3509f84bf3bfd918358e1
add 1.20 exceptions.yaml
commit sha 77d23f77deeafb335c94c62962fd1a12e815d587
Merge pull request #1274 from kikisdeliveryservice/add-120-exceptionsyaml add 1.20 exceptions.yaml
commit sha 376124f79e107a7d44a9eec854b2efac2c2e1e97
Update the branch manager role handbook with additional details
commit sha 42160cd09774bf1cfb6e67ed91a283c5272d1ee2
Address review comments
commit sha 9fce632427a8ebd313d371c9f0a7d2aa1c55d6c7
Add a TODO to remove cip-mm requirement
commit sha 87e75a96db8db9e85ff9cf94c92b0afd1aee7fa0
Merge pull request #1277 from xmudrii/role-handbook-update Update the branch manager role handbook with additional details
commit sha e1257ba9acc0cc1f982ccc03df13716e6f939518
update exceptions.yaml to incl exceptions 10-12 through 10-13
push time in 10 days
Pull request review commentkubernetes/website
Add a technical review requirement for feature documentation
deadlines. 1. Open a pull request against the `dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small commit that you will amend later.-2. Edit the pull request description to include links to `k/k` PR(s) and `k/enhancement` issue(s).+2. Edit the pull request description to include links to `kubernetes/kubernetes` PR(s) and `kubernetes/enhancement` issue(s).
Updated! Thanks for catching that :D
comment created time in 10 days
push eventannajung/website
commit sha edac0b3c2e64fafd7faf2866c4d38ce268c92f43
Modify to change repo names to hyperlinks
push time in 10 days
PR opened kubernetes/website
<!-- 🛈
Hello!
Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.
PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content
Use the default base branch, “master”, if you're documenting existing features in the English localization.
If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.
If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.
-->
- Adds technical review requirement for feature documentation
- Modify to spells out k in
k/kandk/enhancement
pr created time in 10 days
push eventannajung/website
commit sha a2e9bddd90ac076bb65492de2117082d9d2af3cc
Add a technical review requirement for feature documentation
push time in 10 days
push eventannajung/website
commit sha 55892e5367ae0aa7f4a30ae7024d5e96327d5b9c
translate liveness fr
commit sha 293a4ea9d76cd2709a026dd9d90f135165b31c92
translate process namespace fr
commit sha 74af2f19b3c7c5e655cb6966bbdad3e0d898e8f7
fix naming for liveness fr
commit sha 414e1ce8046fdc351b116c744643ff2789aca36f
fix translate share process fr
commit sha 16bbc95df8693330ccf9a6ddd6088144c291a2ab
fix translate liveness and probes fr
commit sha 2a19a35ad9e64319a9473a60dc82b4dffe0fdf2c
grammatical changes to resource metrics pipeline Made some grammatical changes to the text.
commit sha f6eafd9480c0a2119d31b8f18a213d98cd9487d5
Update content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md Avoiding Latin phrasing Co-authored-by: Zach Corleissen <[email protected]>
commit sha 22a5ff9fdb24b7b326244b6e7c1a64a361ed5478
Fix ambiguity around behavior of preStop hook When the previous paragraph says that postStart hooks are fired asynchronously, and this paragraph says "the behavior is much the same for preStop hooks," it reads as saying that preStop hooks are fired asynchronously as well–which is not true. It also seems prudent to give a concrete example of how terminationGracePeriodSeconds applies to the total time it takes the preStop hook and the container shutdown to happen.
commit sha 13fcd40344729a218a1426ffd72da1954ca31292
lowercase container when it's not an API thing Co-authored-by: Tim Bannister <[email protected]>
commit sha 8b2e8df3ad059f983a9e9cc0f16fcd9f613d7405
semicolon and s/they/the/
commit sha 5607db09bb1f58f6eb1ef74e9e21f87df158d9f0
Add important note about port This tutorial should note that the Pod works **only** with `--port=8080`. This would probably save couple of hours for adventurous DevOps trainees.
commit sha b838ea7a3e8f175ba6ab5338a645c2b29d10ad24
Revise node draining task page
commit sha 3d9402e84516b88730dcb3da8d1d874cc288df79
Make docs/reference/scheduling/config focus on v1beta1 over alpha versions Instead of directing the focus towards an alpha API, we now direct it towards the beta API available in 1.19.
commit sha e85fabe3edc6f665b1e74214a496350a3c771dbe
Update horizontal-pod-autoscale-walkthrough.md As per the error described in https://github.com/LevelUpEducation/kubernetes-demo/issues/31, guidance was to add the generator explicitly: `kubectl run --generator=run-pod/v1 -i --tty load-generator --image=busybox /bin/sh` But I prefer the example from the run docs https://jamesdefabia.github.io/docs/user-guide/kubectl/kubectl_run/: `kubectl run -i --tty busybox --image=busybox --restart=Never`
commit sha 390a1c555b2cf0a6216bccfcc75be2fe4fd8a420
Add MP Interactive Tutorial to Config Section
commit sha fda5d0084b540d073f1af733c75ff0e917d4a638
Updates based on feedback
commit sha 235277abcbaf2ef2b149813e6efe26669055e3be
Align Tutorial with new Docs structure
commit sha 7a02c0871e4c724d0033539124b6ebd7dfe2d84e
Remove robo font
commit sha 43c6ce2a5f06adb87da7180e5b4ab7bf8f45e8a9
Remove External Links
commit sha 8dcf08a4d0e4f6c496107137aace89411c3b69de
image does not exist docker pull game.example/demo-game results with Error response from daemon: Get https://game.example/v2/: dial tcp: lookup game.example: no such host. Therefore is better to change image to nginx
push time in 10 days
pull request commentkubernetes/website
Update docs for ServiceAccountIssuerDiscovery beta
friendly ping to @sftim to review this when you can
comment created time in 11 days
pull request commentkubernetes/website
Added docs about container resource metric source for HPA
/hold until k/k PR https://github.com/kubernetes/kubernetes/pull/90691 gets merged in
comment created time in 11 days
pull request commentkubernetes/website
add documentation for system:monitoring rbac policy
Hey @zparnold Can I get your review on this?
I believe technical review from @liggitt stands, just need a review from sig docs and we can get this approved!
comment created time in 11 days
pull request commentkubernetes/website
Update PR template to include a requirment for release related docs
Instead of listing requirement for creating a PR against dev-[future release] branch in the PR template, the "Documenting a feature for a release" doc was modified to include details about adding k/k and k/enhancement links in the PR description and the link to the doc was added to the PR template for a reference.
/hold cancel
comment created time in 12 days
issue commentkubernetes/website
Make container-serve of kubernetes/Website fails on Mac catalina 10.15 - Docker Engine -19.03
@raghvenders I also ran into the same issue failed to extract shortcode: template for shortcode "imgproc" not found when I forgot to run the prerequisites before running the make commands. Running through the steps in prereq resolved the error for me. Can you confirm that you ran through the prereq?
comment created time in 12 days
Pull request review commentkubernetes/website
Update PR template to include a requirment for release related docs
deadlines. 1. Open a pull request against the `dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small commit that you will amend later.-2. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to+2. Edit the pull request description to include links to `k/k` PR(s) and `k/enhancement` issue(s).+3. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
Hi Irvi, are you saying that you would like to see this information in the PR template?
I currently have the link to this doc in the PR template, and I agree with Karen that this may be a lot cleaner approach then to list the requirements in the PR template. What do you think?
comment created time in 12 days
Pull request review commentkubernetes/website
Update PR template to include a requirment for release related docs
deadlines. 1. Open a pull request against the `dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small commit that you will amend later.-2. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to+2. Edit the pull request description to include links to `k/k` PR(s) and `k/enhancement` issue(s).+3. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
AFAIK you need to be part of the website-milestone-maintainer group to be able to be able to add the milestone.
But, I believe the doc is saying people should use the command to notify the docs person managing the release not necessary to add the milestone.
comment created time in 15 days
pull request commentkubernetes/website
Update PR template to include a requirment for release related docs
Hey @kbhawkey, updated the doc and linked it in the PR template. PTAL again when you can
comment created time in 15 days
push eventannajung/website
commit sha 2c31d6a19d87f1d628529f1301ed51b6af3b0e86
Update new feature doc to add a step to include necessary links
push time in 15 days
Pull request review commentkubernetes/website
Update PR template to include a requirment for release related docs
https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice. + Use the next release branch, "dev-x.xx", if you're documenting a feature for+ a release. If applicable, please also include links to k/k and k/enhancement.
Hi @kbhawkey, that's a great idea. I can update the https://kubernetes.io/docs/contribute/new-content/new-features/ doc instead and link the doc here.
As for k/enhancement repo, I already have a PR open for adding docs section in the issue template as well https://github.com/kubernetes/enhancements/pull/2016, but I will also look into where in the docs I can also add this to.
I haven't looked into k/k repo, but I will take a look at that as well.
My intent here was to make sure the PR owner includes k/k and k/enhancement links in the description! :)
comment created time in 15 days
PR opened kubernetes/website
<!-- 🛈
Hello!
Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.
PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content
Use the default base branch, “master”, if you're documenting existing features in the English localization.
If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.
-->
Sig Release docs team often has to track down both k/enhancement and k/k prs related to the doc when it's not shared by the PR owner. Therefore, I like to add a section in the PR template to remind folks about the PR requirements related to the release. (pointing to dev branch and including k/k, k/enhancement links).
During the sig docs meeting, I mentioned creating a separate pull request template, but I think that would just create unnecessary complications since we somehow need to enforce all owners to modify the links to add ?template=templatename at the end of the URL. Therefore, I have decided to add on to the current PR template.
@celestehorgan also brought up an idea about automating this process
- If a k/website PR mentions a k/k issue (or, ideally, PR)
- Then prow applies hold on the k/w PR
- And once the k/k PR is merged, it removes hold ?
I will follow up with someone who is more familiar with prow to see if this is possible!
Regardless of automation, I think a reminder in the PR template could be beneficial.
/hold for feedback from @sftim @jimangel @irvifa
cc @reylejano-rxm @eagleusb @SomtochiAma @kcmartin
pr created time in 15 days
push eventannajung/website
commit sha 95c0162a55b04ef7b16a994a4f42ce57cf25ebff
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 20e237eda7aa85c7f94f7ff3b018867b8e424453
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 4594ffc76f7dc52b2283115fbf1d0039538cfc95
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 535ec2a96bff9d58d951d157d08764db1fcfe5e3
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha b39bc0a5955e11f88675c181e1a5b86485db8383
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 49bcd83aa0fde7c63e6ee90914b9c45bc28597f8
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha d129529f3e44a9ab04a023568e37efe6832665ae
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha f6cba43ba0c3237165649a48ab817e20075a2bde
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha e3fead54c7fa6b7189bb85bcb62ce81ba2023cc1
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha f24da9223599868224430b79e5eba734e82b8feb
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha dcec5a9a06caa8b6128da352352aa077353dbee2
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 9370fcf7ce9651043f604a54735e0a1775639cdc
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 3faf724f24e00f03eb0dc41e4c65714abea2d12c
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha e25015352cdf9c001b4555d70d70d670be5c2f6a
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 6a040a935ffedeba9655b1ff1f42c865f0524c31
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha b04b3dd09727bcaf8cd693662c662cf9f1d990e2
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 3a040fa783ede263e80a14f792b8dc855e4a9ae0
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 629c9ec87e2b09f25635eff327cc917c24041d3e
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha 7215563501ff45a780601a90a186f886fc00e8e7
Update content/zh/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md Co-authored-by: Qiming Teng <[email protected]>
commit sha fc4686c210c2d8015d65e0be1eb2193bdbf88799
Update content/zh/blog/_posts/2018-07-10-coredns-ga.md Co-authored-by: Qiming Teng <[email protected]>
push time in 15 days
push eventannajung/website
commit sha ddeb9944460f846e84a6d528f38b9d20593b9913
Add irvifa as lead as a preparation step for transition
commit sha a0aa5b335625ec89560ca9692e5c4c77af648bb0
update README-it.md
commit sha 10e7a044a2385af56b5ee90e0d01d80f8bdcf343
[zh] Translate declarative-config task
commit sha 8729c6d366b7e882f0f37115da1c3423f1ea6726
fixing language issues on HA-related FR content Signed-off-by: didier <[email protected]>
commit sha 12136358804ba40aa9d49626c227a22390425730
Fix typos
commit sha f4fe5eafd84a31b129ee9affbebcafc8262368ec
Add curl to required packages in kubectl install
commit sha 2ff48e6f42196b0cd6d2098915a67c6d240149d7
Fix typos
commit sha 959d3152f8c3ad2e507fe51531c55c8f7a6c1fbc
Update traefik links in ingress-controllers.md Traefik github repo has been moved from https://github.com/containous/traefik to https://github.com/traefik/traefik. The new company name is `Traefik Labs` and new site https://traefik.io
commit sha 4ad15695d25ffabf0340e97a596bed83981f3702
fix link in intro-windows-in-kubernetes
commit sha 571b8e1bc7ca0222fa1a47ffaa7a83186e6c894a
docs: lost "有" word Signed-off-by: Liu Ming <[email protected]>
commit sha fd97fcd9d58976c8ded4b8bdf65e5adb4507ef07
Add a new known issue to the out-of-resource doc: active_file memory is not considered as available memory
commit sha 80f4942c53a706a1a96d710fe88e3bec564273d8
docs: 缺少右括号 docs: 缺少右括号
commit sha 93c7a1ca43f4ef985b1904aff175d74b1458de9a
add post-filter part
commit sha d63810ded10a4c3035d009c72fd74450164580d3
Add new blog cross-posted from k8s.dev This is crossposted from the Kubernetes Contributor Community blog.
commit sha 2e0c6ba29967d395619e9c4aa5cd20ad88fe18f5
Reduce size of image used on site front page This image of Sarah Wells at KubeCon Europe 2018 makes a large contribution to the overall amount of data loaded for the front page of the site. This commit reduces it to a squashed version that preserves detail in the figure (blurring the background more).
commit sha 5ede1e94c5efbaa7b17221ad4bf0e9b5bb92c835
Correct a type in horizontal-pod-autoscale file None
commit sha f77650a4f68540a4a7266b02726eba73c1160766
Revise style of site front page On the front page of the site, the first paragraph was actually a heading. Replace that with a text paragraph that has a similar style.
commit sha 5416e9f05e92ce1f782e226da1d0de265c3b7096
Clean up gifs under content/zh/docs/setup/production-environment/windows/
commit sha 81f533bc2f40914045728b679d73fa7952a5ed31
Clean up zh controller-metrics.md
commit sha eba9c41d6f3c6cacdd0d627422de64c4af0f2ff2
Clean up zh/docs/concepts/cluster-administration/monitoring.md
push time in 15 days
pull request commentkubernetes/website
add documentation for system:monitoring rbac policy
/hold cancel
comment created time in 16 days
pull request commentkubernetes/website
add documentation for system:monitoring rbac policy
Thank you @logicalhan!
Also, was just reviewing this and if you take a look at the preview https://deploy-preview-22715--kubernetes-io-master-staging.netlify.app/docs/reference/access-authn-authz/rbac/
it actually does not apply ` correctly, and looks like this. It looks like this can be solved using <tt></tt> instead.
comment created time in 16 days
pull request commentkubernetes/website
Promote startupProbe to GA in 1.20
@kbhawkey @sftim @irvifa I think this PR lgtm and can be approved from my perspective. I don't think this it needs a tech review and has been vetted by docs team as well. Just wanted to confirm with you all before proceeding.
comment created time in 16 days
pull request commentkubernetes/website
Merge master into dev-1.20 to keep in sync
Hi @irvifa invalid commit message is a known issue. It happened during out last sync as well (https://github.com/kubernetes/website/pull/24290)
There is an issue open in test-infra to address this (https://github.com/kubernetes/test-infra/issues/17893)
We are currently manually removing the label for now.
In other news, looks like there is a x checkmark next to this commit in the history https://github.com/kubernetes/website/pull/24408/commits/8729c6d366b7e882f0f37115da1c3423f1ea6726 -- clicking on details, I don't see any errors, but second eyes on this will also be helpful!
comment created time in 17 days
pull request commentkubernetes/enhancements
Add Documentation PR section to the issue template
Hi @mrbobbytables @jeremyrickard @justaugustus @johnbelamaric, just a friendly ping to take a look at this when you can! :D
comment created time in 19 days
pull request commentkubernetes/website
add documentation for system:monitoring rbac policy
Hi @logicalhan 1.20 docs lead here, a friendly reminder to update the target branch to dev-1.20.
comment created time in 22 days
pull request commentkubernetes/website
Update docs for ServiceAccountIssuerDiscovery beta
/assign @annajung
comment created time in 22 days
pull request commentkubernetes/website
/assign @annajung
comment created time in 22 days
pull request commentkubernetes/website
Updating doc for setHostnameAsFQDN feature to beta in v1.20
/sig node /assign @annajung /milestone 1.20
comment created time in 22 days
pull request commentkubernetes/website
[WIP] Added docs about container resource metric source for HPA
/milestone 1.20 /assign @annajung
comment created time in 23 days
pull request commentkubernetes/website
Promote startupProbe to GA in 1.20
/milestone 1.20 /assign @annajung
comment created time in 23 days
pull request commentkubernetes/website
/milestone 1.20
comment created time in 23 days
pull request commentkubernetes/sig-release
Add access details and clean up wrong url in docs role handbook
/hold cancel
@savitharaghunathan PTAL, your feedbacks have been addressed
- added details about waiting to divide up enhancement in the tracking sheet until the enhancement freeze
comment created time in 23 days
push eventannajung/sig-release
commit sha b05b87b740ee090ae0347ccccb8f9922d13ea7f8
Add access details and clean up wrong url in docs role handbook
push time in 23 days
pull request commentkubernetes/sig-release
Add access details and clean up wrong url in docs role handbook
/hold
Sorry! Need to add one more thing!
comment created time in 23 days
PR opened kubernetes/sig-release
<!-- Thanks for sending a pull request! Here are some tips for you:
- If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
- Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
- If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
- If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->
What type of PR is this:
/kind cleanup
<!-- Add one of the following kinds: /kind cleanup /kind documentation /kind feature /kind design -->
What this PR does / why we need it:
- Add example PR to get access to
website-milestone-maintainer - Fix broken links
- Update
config.yamlPR with the latest one used in the last release - Add a step to removing the team from
website-milestone-maintainerandsig-docs-en-owners
Which issue(s) this PR fixes:
None
<!--
*Automatically closes linked issue when PR is merged.
Usage: Fixes #<issue number>, or Fixes (paste link of issue).
Fixes # or None -->
Special notes for your reviewer:
/assign @savitharaghunathan @jimangel
pr created time in 23 days
push eventannajung/sig-release
commit sha e6b79306ae823ec4dc679b90d8fde0233c262c8d
Fetch all upstream branches Clarify that one needs to fetch all branches from upstream website repo, not just master branch
commit sha bfed9e48e037b47f753eee7bdcb3fbd51222d451
Adding new step to fetch dev-branch Per PR discussion we don't really need to fetch all branches
commit sha 3fc986867364f1a3417f7c702c5a7f8f1dd8da59
Merge pull request #1266 from kcmartin/patch-1 Clarify instructions to fetch all upstream branches
commit sha a8dc576ff522ebe3c7711343511be2708547ceb8
Add access details and clean up wrong url in docs role handbook
push time in 23 days
push eventannajung/sig-release
commit sha 12fc8b5b537069ede69dfeb29e39139c9f6de799
Add access detals and clean up to docs role handbook
push time in 23 days
push eventannajung/sig-release
commit sha 3728a0ce07bfcc933fbbdd5d4d13d43f8e42b853
Add access detals and clean up to docs role handbook
push time in 23 days
pull request commentkubernetes/sig-release
Clarify instructions to fetch all upstream branches
/lgtm
I'll leave approval to @savitharaghunathan
comment created time in 23 days
issue commentkubernetes/test-infra
@-mentioning a GitHub user in a PR title creates merge commit that Prow then rejects
Hi all, just wanted to raise this issue again since it's happening in the 1.20 release as well.
In addition to @, it looks like we also need to look for # in the PR title as well.
Example:
- https://github.com/kubernetes/website/pull/24290#issuecomment-701713998
- https://github.com/kubernetes/website/pull/24062
cc @jimangel @savitharaghunathan
comment created time in 23 days
pull request commentkubernetes/website
Merge master into dev-1.20 to keep in sync
Thank you @savitharaghunathan!
comment created time in 23 days