You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the downstream clusters require 3 components to be installed: the agent, the client controllers, and the client controller CRDs. In particular the CRDs need to match the version the agent is expecting to install.
The agent plugins are automatically updated, and in the future we will implement updating the agent controllers by updating the agent pod. However this leaves us without a mechanism to update the CRDs.
The crd package in Wrangler may provide a mechanism for doing this. The helm3 controller in k3s currently uses this so we could potentially take inspiration from this:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently the downstream clusters require 3 components to be installed: the agent, the client controllers, and the client controller CRDs. In particular the CRDs need to match the version the agent is expecting to install.
The agent plugins are automatically updated, and in the future we will implement updating the agent controllers by updating the agent pod. However this leaves us without a mechanism to update the CRDs.
The crd package in Wrangler may provide a mechanism for doing this. The helm3 controller in k3s currently uses this so we could potentially take inspiration from this:
We may need to extend this to add the storage versions and conversion webhooks to the CRDs but can be reviewed as part of an OEP
Beta Was this translation helpful? Give feedback.
All reactions