-
Notifications
You must be signed in to change notification settings - Fork 25
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
Rebase 1.31 #60
Rebase 1.31 #60
Conversation
The tests need to be rewritten to be safe for concurrent use and for work in contended environments. Disabling the worst offenders and fixing reuse issues around the tests here. Origin-commit: b6281a54c84f20c2f0d35d6a44881e83b2e75227 Kubernetes-commit: 28d7cd994b1f94603356842e85c034738aacbbdd
Kubernetes-commit: 09525cbe93930c509abec83a7366e227546b421d
Origin-commit: b992ee2fcb5cd610e9242c3165908b6bc6e423f5 UPSTREAM: <carry>: filter out RBR and SCC paths from OpenAPI Origin-commit: 5ce9a77a641ec9d0399226af572e429317d3daf6 UPSTREAM: <carry>: filter out RBR and SCC paths from OpenAPI Origin-commit: 0ee08c7a5e138e8df2bd7d010e9ab59a6543cf63 Kubernetes-commit: c27b04e6a373dd59cf0da17ab5944f653b1a8a1c UPSTREAM: <carry>: fix filtering out CustomResourceQuota paths from OpenAPI surprisingly removing the paths after the spec was built worked in the past. with the upgrade to the new version the paths must be removed before building the spec. Co-authored-by: Lukasz Szaszkiewicz <lukasz.szaszkiewicz@gmail.com>
…ly to admission plugin Kubernetes-commit: 5c0fd14762e63be316b522ed694a65e59fd62056
Origin-commit: beac12d815b4099cfd4f4d953da4b8789054be51 Kubernetes-commit: 4dd78ae36bc5203d4dc46f975e226ffeaadbb203
Origin-commit: c68807a9d7970292a2e9812b9245404938709183 Kubernetes-commit: 954a54fec57a088066ab9ef87935439aa8595d4d
…to genericapiserver Origin-commit: 24960e3b3b0b1805a835a944ae3ba45dc980ce45 Kubernetes-commit: 15571386ecbfa37d6e2185f73dfe07952bc02aa7
Pulls in openshift/kubernetes#1681 and openshift/kubernetes#1676 Note that normally, we would move the patch to a common place and reuse it for kas, oas and oauth, but we are racing against the clock.
…navailable errors for the etcd health checker client
@p0lyn0mial @tkashem PTAL |
@dinhxuanvu did you run into any issues when merging the patches? @dinhxuanvu I see that some e2e tests for openshift-apiserver failed. Are these failures related to changes in this PR? |
No issues during cherry-picking patches for KAS. There are some issues with unit tests on OAS but I'm fixing them up right now. Just upstream changes. No major issues so far. |
mhm, I think that all e2e jobs failed. I checked https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_openshift-apiserver/458/pull-ci-openshift-openshift-apiserver-master-e2e-aws-ovn/1853871937520930816/artifacts/e2e-aws-ovn/gather-extra/artifacts/pods/openshift-apiserver_apiserver-65bf844bcb-rm9sj_openshift-apiserver.log and it looks like that OAS didn't start due to:
I think we should ensure at least some e2e tests pass to confirm that the changes in this PR are correct and no further changes are needed before merging. WDYT? |
I pushed some changes. I expect unit tests to pass now and we can see some clear signals on e2e. Let see if we bump into any issues. When CI is green on OAS, we can merge KAS. |
the proof pr is green /lgtm |
@p0lyn0mial Ready for merge. |
0f10e42
into
openshift:openshift-apiserver-4.18-kubernetes-1.31.1
Cherry-pick carry patches to 4.18/1.31