This PR will fail CI if the operator CRDs are not in sync.
This is potentially annoying, as it means we may need to push some
unrelated changes into PRs to get CI working. But I think it is worth
the friction to avoid these getting out of sync.
We have encountered release problems in the past where we shipped
operator CRDs that were out of date.
Related issues/PRs
Todos
[ ] Tests
[ ] Documentation
[ ] Release note
Release Note
TBD
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.
docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.
Every PR needs one release-note-* label.
release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.
Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.
Description
Fixes https://github.com/projectcalico/calico/issues/8883
This PR will fail CI if the operator CRDs are not in sync.
This is potentially annoying, as it means we may need to push some unrelated changes into PRs to get CI working. But I think it is worth the friction to avoid these getting out of sync.
We have encountered release problems in the past where we shipped operator CRDs that were out of date.
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*label.docs-pr-required: This change requires a change to the documentation that has not been completed yet.docs-completed: This change has all necessary documentation completed.docs-not-required: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*label.release-note-required: This PR has user-facing changes. Most PRs should have this label.release-note-not-required: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.