Skip to content
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

Bug 1986003: Bump k8s.io to 1.22.0-rc.0 #862

Merged
merged 3,138 commits into from Aug 10, 2021

Conversation

soltysh
Copy link
Member

@soltysh soltysh commented Jul 20, 2021

liggitt and others added 30 commits July 8, 2021 02:19
Make messages consistent
Add unit tests for messages
Consolidate integration test fixtures
Rename to seccompProfile_baseline
Add documentation and unit tests for messages
rename to seLinuxOptions
make message consistent
add unit tests for message
consolidate integration test fixtures
Drop hashicorp lru - switch to the lru impl in k8s.io/utils
…image-pull

kubeadm: statically default the "from cluster" InitConfiguration
…finements

Refinements to pick queue logic in P&F
…erm-test

Clean up the remaining master names in test/integration
…onfiguration

[PodSecurity] Add ValidatePodSecurityConfiguration
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
…location

 fix translations location in update-translations.sh
…pdate-allocs

Service: Fix semantics for Update wrt allocations
fix CleanScope so we can resolve correct verb for apiserver_request_terminations_total
With the introduction of GVK to the fake dynamic client it made using
the fake much more cumbersome.

Specifically:
- requires manual registration of list types
- mismatch between scheme types and passed in fixtures would result in errors

The PR changes the constructor method NewSimpleDynamicClient to do the following:
- rewire the schemes to unstructured types
- typed fixtures are converted to unstructured types
- automatically register fixture gvks with the scheme

This should make the dynamic client 'flexible' with it's inputs like it was
before
For tracking Job Pods that have finished but are not yet counted as failed or succeeded

And feature gate JobTrackingWithFinalizers

Change-Id: I3e080f3ec090922640384b692e88eaf9a544d3b5
…ubernetes#102503)

* kubectl: update set command description to include cronjob resource

* kubectl: update set command description to include statefulset resource

* kubectl: update set env description to remove job from resources that can update container env

* kubectl set tests: add cronjob resource and remove job resource

* go fmt
…ng-script-for-forked-code

Update license gathering script for forked code
…n-api

Add Job.status.uncountedTerminatedPods for Job tracking
Through Job.status.uncountedPodUIDs and a Pod finalizer

An annotation marks if a job should be tracked with new behavior

A separate work queue is used to remove finalizers from orphan pods.

Change-Id: I1862e930257a9d1f7f1b2b0a526ed15bc8c248ad
@soltysh
Copy link
Member Author

soltysh commented Aug 10, 2021

/test e2e-gcp-upgrade

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@soltysh
Copy link
Member Author

soltysh commented Aug 10, 2021

/test e2e-aws-fips

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@soltysh
Copy link
Member Author

soltysh commented Aug 10, 2021

/test e2e-gcp-upgrade

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link

openshift-ci bot commented Aug 10, 2021

@soltysh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-agnostic-cmd 67dde66 link /test e2e-agnostic-cmd

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.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci openshift-ci bot merged commit 9b1230e into openshift:master Aug 10, 2021
@openshift-ci
Copy link

openshift-ci bot commented Aug 10, 2021

@soltysh: All pull requests linked via external trackers have merged:

Bugzilla bug 1986003 has been moved to the MODIFIED state.

In response to this:

Bug 1986003: Bump k8s.io to 1.22.0-rc.0

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet