New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.22.1 rebase #914
1.22.1 rebase #914
Conversation
This assumes that SSH via bastion works if the `KUBE_SSH_BASTION` environment variable is set, which is the case for `pull-kubernetes-e2e-gce-correctness`. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
…rry-pick-of-#103806-upstream-release-1.22 Automated cherry pick of kubernetes#103806: Fetch metrics from controller manager & scheduler no run once
use deployment based on upstream manifest - add liveness and readiness probes - use kubelet port secure port https://github.com/kubernetes-sigs/metrics-server/blob/release-0.4/manifests/base/deployment.yaml#L32-L38
That PR fixes --audit-log-path=- support. It now logs to stdout as in 1.21.
The commands used were (roughly): hack/pin-dependency.sh github.com/opencontainers/runc v1.0.1 hack/lint-dependencies.sh # Follow its recommendations. hack/pin-dependency.sh github.com/cilium/ebpf v0.6.2 hack/pin-dependency.sh github.com/opencontainers/selinux v1.8.2 hack/pin-dependency.sh github.com/sirupsen/logrus v1.8.1 # Recheck. hack/lint-dependencies.sh GO111MODULE=on go mod edit -dropreplace github.com/willf/bitset hack/update-vendor.sh # Recheck. hack/lint-dependencies.sh hack/update-internal-modules.sh # Recheck. hack/lint-dependencies.sh Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Since runc 1.0.0 it is now sufficient to have SkipDevices: true. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
…-of-#103713-upstream-release-1.22 Automated cherry pick of kubernetes#103713: cluster: fix CI metrics-server deployment
…cherry-pick Do not try to create an audit log file named "-"
…pick-of-#103743-upstream-release-1.22 Automated cherry pick of kubernetes#103743: vendor: bump runc to 1.0.1
Includes a fix to prevent the agent writing to a closed channel.
…rry-pick-of-#103815-upstream-release-1.22 Automated cherry pick of kubernetes#103815: Fix SIG Node SSH e2e test
…ck-of-#103823-upstream-release-1.22 Automated cherry pick of kubernetes#103823: Make CSR cleaner tolerate objects with invalid
…ck-of-#103831-upstream-release-1.22 Automated cherry pick of kubernetes#103831: disable aufs module
Ref: https://kubernetes.slack.com/archives/C0BP8PW9G/p1627003199187100?thread_ts=1626988113.184100&cid=C0BP8PW9G Signed-off-by: Nabarun Pal <pal.nabarun95@gmail.com>
…ick-of-#103895-upstream-release-1.22 Automated cherry pick of kubernetes#103895: Update to using apiserver-network-proxy v1.22
This PR fixes two distruptive subpath test failures. 1. disable --check-volume-lifecycle check 2. skip hostpath driver tests on graceful pod deletion test too. See details in kubernetes#103651 (comment) Change-Id: Ibecd051be865feea5f2a92d22ade848367400939
…-pick-of-#103865-upstream-release-1.22 Automated cherry pick of kubernetes#103865: Add e2e testing manifest bundle to e2e_node test suite
…-pick-of-#103439-upstream-release-1.22 Automated cherry pick of kubernetes#103439: fix azure disk translation issue
…ick-of-#103937-upstream-release-1.22 Automated cherry pick of kubernetes#103937: Fix disruptive subPath test failures
…-pick-of-#103827-upstream-release-1.22 Automated cherry pick of kubernetes#103827: Remove conformance status from a sysctl test and relabel
…am range to 0-10s"
…pick-of-#104033-upstream-release-1.22 Automated cherry pick of kubernetes#104033: Revert "Add a namespace label to admission metrics and expand
…a.crt for migration compatibility
…getting less secure
UPSTREAM: <carry>: 1.21 alpha & other tests disablement UPSTREAM: <carry>: Enable GenerciEphemeralVolume tests UPSTREAM: <carry>: Re-enable [Feature:NetworkPolicy] tests which were wrongly disabled in rebase UPSTREAM: <carry>: Reenable NetworkPolicy test Signed-off-by: Mohamed Mahmoud <mmahmoud@redhat.com> UPSTREAM: <carry>: Conformance tests (sysctls) should be run We have to run this test for conformance, and the tests pass. Reenable this block which has been disabled for 2 releases (but appears to work fine). UPSTREAM: <carry>: Don't force-disable IPv6, dual-stack, and SCTP tests Instead, openshift-tests will enable or disable them depending on cluster configuration. UPSTREAM: <carry>: update Multi-AZ Cluster Volumes test name This test was renamed upstream in kubernetes@006dc74
…n pods are quickly deleted
The tag extraction from GOFLAGS doesn't do anything if -tags is not present in GOFLAGS. Not only does that mean non-sensical tags are passed, but because GOFLAGS is a space-separated variable, the build will fail because the build flags because -tags must be comma-separated. Signed-off-by: Yaakov Selkowitz <yselkowi@redhat.com>
Introduce a new server run option startup-send-retry-after-until-ready If true, incoming request(s) will be rejected with a '429' status code and a 'Retry-After' response header until the apiserver has initialized. This option ensures that the system stays consistent even when requests arrive at the server before it has been initialized. The default value is set to 'false' to maintain current behavior.
During a bump to k8 ver. 1.22.0, networking tests were disabled to accomplish the bump. This disabled netpol and older network tests. Netpol tests will be enabled in a following PR and therefore only partially fixes BZ. This commit partially fixes bug 1986307. https://bugzilla.redhat.com/show_bug.cgi?id=1986307 Signed-off-by: Martin Kennelly <mkennell@redhat.com>
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1986307 Signed-off-by: Martin Kennelly <mkennell@redhat.com>
…getting false positives until the server becomes ready the availability checks depend on fully initialized SDN OpenShift carries a few reachability checks that affect /readyz protocol we skip posting failures to avoid getting false positives until the server becomes ready
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: damemi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@damemi: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@damemi: PR needs rebase. 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. |
/close |
@damemi: Closed this PR. 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. |
Replacing #913
This was made following the steps in https://github.com/openshift/kubernetes/blob/master/REBASE.openshift.md
Commits link: https://docs.google.com/spreadsheets/d/1SNumGZ-ojXyohqwW3s00ODqOguWPwFxX/edit?usp=sharing&ouid=108595573157330081526&rtpof=true&sd=true
Steps:
then when running the
make update
command (docker run -it --rm -v $( pwd ):/go/k8s.io/kubernetes:Z --workdir=/go/k8s.io/kubernetes registry.ci.openshift.org/openshift/release:rhel-8-release-golang-1.16-openshift-4.8 make update OS_RUN_WITHOUT_DOCKER=yes
) I get the following failure: