Merged main into dev 1.29 branch #43682
Conversation
…md_update Add note after restore cmd to specify that data-dir will be (re)created
Update connect-applications-service.md
…ats_next what's next for network plugin
* Small mistake between sections of the document The note for --kube-reserved-cgroup should match formatting for --system-reserved-cgroup. This changes helps those match. * Update reserve-compute-resources.md --------- Co-authored-by: Qiming Teng <[email protected]>
Update connect-applications-service.md
…odaffinity Fix example errors for CrossNamespacePodAffinity
…ansition-time Add blog for PersistentVolume last phase transition time
* Remove redudant steps from instruction * Update content/en/docs/tutorials/services/connect-applications-service.md Co-authored-by: Michael <[email protected]> * Update content/en/docs/tutorials/services/connect-applications-service.md Co-authored-by: Michael <[email protected]> * Update content/en/docs/tutorials/services/connect-applications-service.md Co-authored-by: Michael <[email protected]> * Update content/en/docs/tutorials/services/connect-applications-service.md Co-authored-by: Michael <[email protected]> * Update content/en/docs/tutorials/services/connect-applications-service.md Co-authored-by: Tim Bannister <[email protected]> * Update content/en/docs/tutorials/services/connect-applications-service.md Co-authored-by: Michael <[email protected]> * Change line 313, and add missing line * Fix missing command end on line 313 * Update connect-applications-service.md --------- Co-authored-by: Michael <[email protected]> Co-authored-by: Tim Bannister <[email protected]> Co-authored-by: Qiming Teng <[email protected]>
Clarify IBM Java and IBM Semeru Runtimes cgroupsV2 support
Include `initContainers` in list-all-running-container-images.md
[pl] Updated resources of README.md
…ption Add -subj Command Option.
Document deprecated leader annotation
Correct `collection` definition to a list of instances of a resource _type_
Added secret keyword to kubectl-command.html file
kubectl/jsonpath: add example of escaping termination character
Fixed the reference link for 'secret permissions with default mode'
…ging-tls-in-a-cluster
[zh] sync list-all-running-container-images reserve-compute-resources managing-tls-in-a-cluster
The `krel` templates are the ones we use right now, while kubepkg got removed in kubernetes/release#3313. Signed-off-by: Sascha Grunert <[email protected]>
Package builds are now integrated into `krel obs`, means we do not have to reference rapture any more. It also got removed in kubernetes/release#3313. Signed-off-by: Sascha Grunert <[email protected]>
Remove rapture reference for build admins
…es#43394) * doc(etcd-maintenance): add reference to etcd-defrag CronJob * doc: improve style according to style guide * chore: fix file name
Signed-off-by: xin.li <[email protected]>
Signed-off-by: xin.li <[email protected]>
Signed-off-by: xin.li <[email protected]>
|
@caesarxuchao @bgrant0607 could you kindly review this PR and give your approval if everything looks good to you? Warm regards. |
k8s-ci-robot
added
the
approved
|
/approve |
|
/check-cla |
|
Hmm, I wonder what EasyCLA is playing at. |
|
CI appears to be haunted |
|
/easycla |
1 similar comment
|
/easycla |
|
|
|
/check-cla |
|
/retest |
|
/easycla |
|
/check-cla |
|
/approve (Steering) nudges bots: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justaugustus, pacoxu, palnabarun, sftim, tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
While we're waiting... how about a: |
|
@justaugustus: What do you call a cow with two legs? Lean beef. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Just out of curiosity ... since when the sync from main to a dev-1.xx branch needs an upcall to the steering committee, and even a quorum from the committee? The committee has no other important works to oversee or we are really trying to improve something? I can smell something bad from this based on what I witnessed somewhere else. A truly open community encourages all open contributions, open discussions and open collaborations. Redundant rules. policies or processes are invented and enforced only when there are no other choices. If there is a trend towards more bureaucracy rather than more productivity, please let us watch out and think twice. Does this PR really worth your precious time? |
|
We do not usually need steering involvement to merge branch syncs. This PR requires it because it merges a site banner, and those require approval from steering. Please be kind. |
Sorry for being ignorance about this exception. I was hoping that we as a community foster more trusts to contributors and motivates them rather than spending time on rules, processes. |
|
/easycla |
1 similar comment
|
/easycla |
|
/check-cla |
|
Per the discussion https://kubernetes.slack.com/archives/C1TU9EB9S/p1698411010005219?thread_ts=1698411010.005219&cid=C1TU9EB9S, going ahead and manually merging the PR. |
This PR syncs the dev-1.29 branch with main to keep the dev-1.29 branch up to date.
cc: @katcosgrove @taniaduggal @drewhagen @harshitasao