k8s 1.25.0 #1360
k8s 1.25.0 #1360
Conversation
…nges Update CRI API to support Evented PLEG
…ges for kubelet client and serving certificates Signed-off-by: Paco Xu <paco.xu@daocloud.io>
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
It is used to request that a pod runs in a unique user namespace. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com> Co-authored-by: Rodrigo Campos <rodrigoca@microsoft.com>
Move e2e test from alpha with feature promoted to beta
…ment Allow retroactive storage class assigment to PVCs
KEP: /enhancements/keps/sig-node/1287-in-place-update-pod-resources
Promote CronJobTimeZone to beta
Change-Id: I3be351fb3b53216948a37b1d58224f8fbbf22b47
…uceeded Fix JobTrackingWithFinalizers when a pod succeeds after the job fails
…ional modify the signing/approving controller to tolerate either set of usages for kubelet client and serving certificates
….12.1, kustomize/v4.5.7 (kubernetes#111606)
Signed-off-by: Abirdcfly <fp544037857@gmail.com>
…ertical-scaling-cri CRI changes to support in-place pod resize
This change is to promote local storage capacity isolation feature to GA At the same time, to allow rootless system disable this feature due to unable to get root fs, this change introduced a new kubelet config "localStorageCapacityIsolation". By default it is set to true. For rootless systems, they can set this configuration to false to disable the feature. Once it is set, user cannot set ephemeral-storage request/limit because capacity and allocatable will not be set. Change-Id: I48a52e737c6a09e9131454db6ad31247b56c000a
modify modify modify modify modify
define a feature gate for the user namespaces support. The feature is not enabled by default. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
e2e: Trim junit reporter to adapt with testgrid
…d-arch-installing-etcd Avoid hard coding Operating System and Architecture in hack/lib/etcd.sh
…im_report Revert "e2e: Trim junit reporter to adapt with testgrid"
Including the full information for successful tests makes the resulting XML file too large for the 200GB limit in Spyglass when running large jobs (like scale testing). The original solution from kubernetes#111627 broke JUnit reporting in other test suites, in particular test/e2e_node. Keeping the code inside the framework ensures that all test suites continue to have the JUnit reporting. AfterReadingAllFlags is a good place to set this up because all test suites using the test context are expected to call it before running tests and after parsing flags. Removing the ReportEntries added by ginkgo.By from all test reports usually avoids the `system-err` part in the JUnit file, which in Spyglass avoids the extra "open stdout" button. Co-authored-by: Patrick Ohly <patrick.ohly@intel.com> Co-authored-by: Dave Chen <dave.chen@arm.com>
Signed-off-by: David Porter <david@porter.me>
This commit just adds a validation according to KEP-127. We check that only the supported volumes for phase 1 of the KEP are accepted. Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>
it is used to allocate and keep track of the unique users ranges assigned to each pod that runs in a user namespace. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com> Co-authored-by: Rodrigo Campos <rodrigoca@microsoft.com>
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
@soltysh: trigger 4 job(s) of type blocking for the ci release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/20942250-3b68-11ed-9dc8-a45c8f949065-0 trigger 6 job(s) of type blocking for the nightly release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/20942250-3b68-11ed-9dc8-a45c8f949065-1 |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-bm |
|
@kikisdeliveryservice: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c04faa20-3b8c-11ed-8d2d-2a010aa8f9ef-0 |
|
/payload 4.12 ci blocking |
|
@kikisdeliveryservice: trigger 4 job(s) of type blocking for the ci release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6924b890-3b9a-11ed-93d6-6efda718b26d-0 |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-bm |
|
@soltysh: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c2fe2c00-3cc3-11ed-8a91-8a66f1caa3c2-0 |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-bm |
|
@soltysh: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f3911200-3d8c-11ed-889b-ee6d9d0410d3-0 |
|
/payload 4.12 ci blocking |
|
@soltysh: trigger 4 job(s) of type blocking for the ci release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b5aec500-3db8-11ed-9817-e48baffb7c47-0 trigger 6 job(s) of type blocking for the nightly release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b5aec500-3db8-11ed-9817-e48baffb7c47-1 |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade 10 |
|
@kikisdeliveryservice: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/862666f0-3dfc-11ed-838b-35e4cc0b9870-0 |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade 10 |
1 similar comment
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade 10 |
|
@soltysh: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3691e400-3e2b-11ed-910b-cce3c44c2163-0 |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.12-upgrade-from-stable-4.11-e2e-metal-ipi-bm-upgrade |
|
@derekhiggins: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a8369100-3e44-11ed-8504-5dc93e0db41c-0 |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade 15 |
|
@soltysh: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bdd1c320-3e50-11ed-9b43-f4c4f37bf6ae-0 |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.12-upgrade-from-stable-4.11-e2e-metal-ipi-bm-upgrade |
|
@derekhiggins: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3a614770-3e6b-11ed-9bc3-be00554d4116-0 |
This test doesn't have a high pass rate - sippy points it at ~25%. The ingress-to-console failure (from this run) is also a known issue. |
|
last run of ovn upgrade job: /payload-aggregate periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade 15 |
|
@kikisdeliveryservice: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a1b544d0-3e84-11ed-8228-92815873b89f-0 |
hmm i thought we were giving more time but it still ends at 4.5hr. 🤷 Interestingly we got 4:11 success but 4 unfinished. I have a morbid curiosity so just running with 10. /payload-aggregate periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn-upgrade 10 |
|
@kikisdeliveryservice: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c3518820-3eb0-11ed-9ca2-2081fac936ff-0 |
|
merging as agreed. |
Picks: https://docs.google.com/spreadsheets/d/10KYptJkDB1z8_RYCQVBYDjdTlRfyoXILMa0Fg8tnNlY/edit#gid=1852049954
Test tracker: https://docs.google.com/spreadsheets/d/1KuC8QAmQd2LiCMk0EVBxss97V0-UNtFM8vVEqPYWCqs/edit#gid=1312057609