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
Remove deprecated CiliumEndpoint fields #10509
Conversation
These fields have been deprecated in Cilium 1.4 and were scheduled for removal in 1.5. Remove them for 1.8. Signed-off-by: Thomas Graf <thomas@cilium.io>
This state no longer exists and has not been in use for a while, remove it. Signed-off-by: Thomas Graf <thomas@cilium.io>
test-me-please
|
test-me-please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the endpoint status structure is being modified we need to bump
CustomResourceDefinitionSchemaVersion = "1.16" |
Also, by bumping that version, we will brake downgrade path as that structure will no longer exist if the user wants to downgrade from 1.8 to 1.7.
I would only keep the changes in pkg/endpoint/endpoint_status.go
plus the version upgrade and remove the deprecated fields from EndpointStatus
later on probably once we don't support downgrade to 1.8 (possibly in 1.10)
Why does it need to be bumped? None of the fields are changing. The CRV remains identical. Why would downgrade break? If an upgrade occurred then the old CEP CRD is already registered so it will be unchanged and rollback is possible. The removed fields have been marked as deprecated for a long time and no code should depend on it. If it depends on them, it should break. |
I had the impression that we had a CRV for CEP. |
Thanks for double checking |
This change is