Bug 1986003: Rebase 1.22.1 #916
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
|
/override ci/prow/verify-commits |
|
@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits 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. |
|
/override ci/prow/verify-commits |
|
@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: soltysh, sttts 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 |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/override ci/prow/e2e-agnostic-cmd |
|
/bugzilla refresh |
|
@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-agnostic-cmd 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. |
|
@soltysh: An error was encountered querying GitHub for users with public email (kewang@redhat.com) for bug 1986003 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
non-200 OK status code: 403 Forbidden body: "{\n \"documentation_url\": \"https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\",\n \"message\": \"You have exceeded a secondary rate limit. Please wait a few minutes before you try again.\"\n}\n"
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
|
/bugzilla refresh |
1 similar comment
|
/bugzilla refresh |
openshift-ci
bot
added
bugzilla/severity-high
|
@sttts: This pull request references Bugzilla bug 1986003, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
Alternative to #914
/assign @mfojtik @sttts @damemi