jayunit100
commented
2 years ago per conversation w/ amim, this might completley break TCE so im closing this issue :)
Closed jayunit100 closed 2 years ago
jayunit100
commented
2 years ago per conversation w/ amim, this might completley break TCE so im closing this issue :)
Right now we have a very restrictive schema in antrea 1.2.3 . This can have dangerous, uninteded consequences that can prevent people from upgrading properly - and thus - bring down clusters during upgrade scenarios.
The value of a restrictive schema, during this phase of TCE, for something critical such as CNIs, isnt very high.
https://github.com/vmware-tanzu/community-edition/blob/main/addons/packages/antrea/1.2.3/bundle/config/schema.yaml
And also in calico.
We'd like to keep the CNIs schemaless for backwards compatibility for the time being, since they play a critical role in the upgrade of clusters.
In cases where older versions are being incrementally upgraded, it would be unfortunate for us to have to put data mangling code into TCE required for managing old versions of CNIs... and it would be hard to test all upgrade paths.
Additionally being able to have flexibility to plumb optional features that are undocumented into CNIs has some value in terms of testing bleeding edge components.
Other options
We can put custom code in the controllers for the add ons if we want that are backwards compatible.