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

⚠ bump to kubernetes 1.22.1, remove support for legacy v1beta1 CRDs and webhooks #607

Merged
merged 1 commit into from
Sep 19, 2021

Conversation

joelanford
Copy link
Member

This PR bumps controller-tools k8s dependencies to 1.22.1

This is a breaking change. It removes support for v1beta1 CRDs and webhooks. These APIs are no longer served in 1.22.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 31, 2021
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 31, 2021
Copy link
Member

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work @joelanford 👍

Just checking if we can get merge and do a release :-)

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Sep 17, 2021
@camilamacedo86 camilamacedo86 removed lgtm "Looks good to me", indicates that a PR is ready to be merged. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Sep 17, 2021
Copy link
Member

@alvaroaleman alvaroaleman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 17, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alvaroaleman, camilamacedo86, joelanford

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:
  • OWNERS [alvaroaleman,joelanford]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@camilamacedo86
Copy link
Member

/test pull-controller-tools-test-master

@alvaroaleman
Copy link
Member

/hold
failure is genuine, there is some dead code left

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 17, 2021
@camilamacedo86
Copy link
Member

camilamacedo86 commented Sep 19, 2021

Hi @alvaroaleman,

Yes. That fails with the master rebase only. So, that seems that was missing a rebase,

Hi @joelanford,

Thank you to push the changes.

@camilamacedo86
Copy link
Member

/hold cancel
/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Sep 19, 2021
@k8s-ci-robot k8s-ci-robot merged commit 9724ec3 into kubernetes-sigs:master Sep 19, 2021
@joelanford joelanford deleted the k8s-1.22 branch September 20, 2021 01:32
AlexanderYastrebov added a commit to AlexanderYastrebov/controller-tools that referenced this pull request Apr 10, 2024
Reinstate crd:preserveUnknownFields option removed by kubernetes-sigs#607
to allow specifying the value of deprecated spec.preserveUnknownFields
CRD field.

This is useful for updating CRDs that were automatically converted from
v1beta1 version which had true as a default value and resulted in:
```
$ kubectl get crd foo.bar -o yaml | grep preserveUnknownFields
  preserveUnknownFields: true
    message: 'spec.preserveUnknownFields: Invalid value: true: must be false'
```

Fixes kubernetes-sigs#476
AlexanderYastrebov added a commit to AlexanderYastrebov/controller-tools that referenced this pull request Apr 10, 2024
Reinstate crd:preserveUnknownFields option removed by kubernetes-sigs#607
to allow specifying the value of deprecated spec.preserveUnknownFields
CRD field.

This is useful for updating CRDs that were automatically converted from
v1beta1 version which had true as a default value and resulted in:
```
$ kubectl get crd foo.bar -o yaml | grep preserveUnknownFields
  preserveUnknownFields: true
    message: 'spec.preserveUnknownFields: Invalid value: true: must be false'
```

For kubernetes-sigs#476
AlexanderYastrebov added a commit to AlexanderYastrebov/controller-tools that referenced this pull request Apr 11, 2024
Reinstate crd:preserveUnknownFields option removed by kubernetes-sigs#607
to allow specifying the value of deprecated spec.preserveUnknownFields
CRD field.

This is useful for updating CRDs that were automatically converted from
v1beta1 version which had true as a default value and resulted in:
```
$ kubectl get crd foo.bar -o yaml | grep preserveUnknownFields
  preserveUnknownFields: true
    message: 'spec.preserveUnknownFields: Invalid value: true: must be false'
```

For kubernetes-sigs#476
AlexanderYastrebov added a commit to AlexanderYastrebov/controller-tools that referenced this pull request Apr 15, 2024
Reinstate crd:preserveUnknownFields option removed by kubernetes-sigs#607
to allow specifying the value of deprecated spec.preserveUnknownFields
CRD field.

This is useful for updating CRDs that were automatically converted from
v1beta1 version which had true as a default value and resulted in:
```
$ kubectl get crd foo.bar -o yaml | grep preserveUnknownFields
  preserveUnknownFields: true
    message: 'spec.preserveUnknownFields: Invalid value: true: must be false'
```

For kubernetes-sigs#476
k8s-ci-robot pushed a commit that referenced this pull request Apr 19, 2024
* crd: allow specifying spec.preserveUnknownFields

Reinstate crd:preserveUnknownFields option removed by #607
to allow specifying the value of deprecated spec.preserveUnknownFields
CRD field.

This is useful for updating CRDs that were automatically converted from
v1beta1 version which had true as a default value and resulted in:
```
$ kubectl get crd foo.bar -o yaml | grep preserveUnknownFields
  preserveUnknownFields: true
    message: 'spec.preserveUnknownFields: Invalid value: true: must be false'
```

For #476

* crd: rename marker to DeprecatedV1beta1CompatibilityPreserveUnknownFields
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants