Bug 2086092: update kube to v1.24.0 #1252
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 61b3c02.
Revert "Field `status.hostIPs` added for Pod (kubernetes#101566)"
Some Azure regions do not have any availability zones. Nodes in such zones have
these labels, where "0" is a fault domain, not an availability zone.
"topology.kubernetes.io/region": "westus"
"topology.kubernetes.io/zone": "0"
Azure Disk CSI driver uses zone "" in this case:
"topology.disk.csi.azure.com/zone": ""
Fix the CSI translation to translate the fault domain "0" to "". Any value that is just
a number and not "<region>-<number>" ("centralus-1") needs to be translated to
"" in similar fashion.
Fix non-enum CSR condition field, omit enums from static openapi snapshot
Fix copylock vet errors in component-base metrics
Exercise defaulting tests with/without features enabled
…r-migration-v1-api v1 types for Leader Migration
…ted_requests Fix the overestimated cost of deletaged API requests in P&F
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
Add sync_proxy_rules_no_endpoints_total metric
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
compact scheduling failure msg for taint/toleration mismatch
set parallelism in integration tests using GOMAXPROCS
…dation-tests Flake fix: validate each expression once in primary CEL correctness suite
…me-data-structures-from-gotestsum Correctly attribute some data structures from gotestsum repository
In the tests, we oftentimes create pods directly by the administrative user and so their SCC-related privileges are being used to create the pods. The PSa label syncher however works by introspecting SAs in each namespace, and since the SAs in the direct pod creation use-cases don't have the SCC-related privileges, the labelsyncer evaluates these namespaces as "restricted" because only the "restricted-v2" SCC is ever assigned in the namespaces. This breaks tests where pods are created directly. openshift-rebase(v1.24):source=35dc012e1f5
we encountered a vendor inconsistency error from staging/src/k8s.io/code-generator.
in order to fix it:
- change direcroty to 'staging/src/k8s.io/code-generator/examples'
- open go.mod and add openshift ginkgo in a replace section
replace (
github.com/onsi/ginkgo => github.com/openshift/ginkgo origin-4.7
)
- go mod tidy
- change directory to 'staging/src/k8s.io/code-generator'
- open go.mod and add openshift ginkgo in a replace section
replace (
github.com/onsi/ginkgo => github.com/openshift/ginkgo origin-4.7
)
- go mod tidy
- go mod vendor
- change directory to root of the repo
- bump the following openshift repos in the go.mod file
- openshift/api
- openshift/client-go
- openshift/library-go
- openshift/apiserver-library-go
- github.com/openshift/ginkgo origin-4.7
- go mod tidy
- hack/update-vendor.sh
when we run verify-import-boss.sh it fails with the following error errors in package "k8s.io/kubernetes/cmd/kubeadm/app/phases/bootstraptoken/node": the following imports did not match any allowed prefix: gopkg.in/yaml.v3 k8s.io/kube-openapi/pkg/validation/spec note: this should be an upstream fix, not sure why we don't see this error in upstream, does upstream not run this job in verify? investigate and take proper action for this commit
make update fails with the following error due to some go mod issue
in code-generator:
```
inconsistent vendoring in /go/{redacted}/k8s.io/code-generator
```
to work around, we do the following:
- change directory to 'staging/src/k8s.io/code-generator'
- remove the following from the 'replace' section
k8s.io/code-generator => ../code-generator
- run 'go mod tidy'
- run 'go mod vendor'
- change directory to root
- run make update, using the following command
podman run -it --rm -v $( pwd ):/go/src/k8s.io/kubernetes:Z \
--workdir=/go/src/k8s.io/kubernetes \
registry.ci.openshift.org/openshift/release:rhel-8-release-golang-1.18-openshift-4.11 \
make update OS_RUN_WITHOUT_DOCKER=yes
inside the docker prompt, also run the followig:
- OS_RUN_WITHOUT_DOCKER=yes hack/update-generated-pod-resources.sh
due to the following inconsistent vendoring error: go: inconsistent vendoring in /go/src/k8s.io/kubernetes/hack/tools: we need to do the following steps: - change directory to 'hack/tools' - run 'go mod tidy' - run 'go mod vendor' - run 'update-netparse-cve.sh' if you are inside the container, then: OS_RUN_WITHOUT_DOCKER=yes hack/update-netparse-cve.sh
due to the following inconsistent vendoring error: go: inconsistent vendoring in /go/src/k8s.io/kubernetes/hack/tools: we need to do the following steps: - change directory to 'hack/tools' - run 'go mod tidy' - run 'go mod vendor' - run 'update-mocks.sh' if you are inside the container, then: OS_RUN_WITHOUT_DOCKER=yes hack/update-mocks.sh we also need to check in the vendr folder, otherwise the verify mock job will fail in ci note: why does verify mocks fail with upstream file that we have not changed? further investigate warranted.
due to the following inconsistent vendoring error: go: inconsistent vendoring in /go/src/k8s.io/kubernetes/hack/tools: we run make update by removing the following from replace section of code-generator go.mod file k8s.io/code-generator => ../code-generator so after we complete all 'update', we run hack/update-vendor.sh once we solve the dependency issue with downstream then this would no longer be needed
- disable 'ProxyTerminatingEndpoints' feature e2e tests - disable [sig-network] [Feature:Topology Hints] should distribute endpoints evenly see https://bugzilla.redhat.com/show_bug.cgi?id=2079958 for more context
…ice account token should be auto-generated
|
/retest |
|
@tkashem: Some pull requests linked via external trackers have merged:
The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with Bugzilla bug 2086092 has not been moved to the MODIFIED state. 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. |
|
@tkashem: 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. |
This was referenced Jun 1, 2022
This was referenced Jun 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.