7cbe564ff1
This patch drops the custom caching of the Cozystack resource definitions in favor of the informer cache and adds a flag to the Cozystack controller to select, whether it restarts the cozystack-api deployment or the cozystack-api daemonset. As with the new default behavior of using a local endpoint for the k8s API by the lineage webhook and the Cozystack API, the Cozystack controller now also defaults to restarting a Cozystack API DaemonSet instead of a Deployment. To revert to the old behavior, disable the local k8s API endpoint on the webhook and cozystack API and set the `cozystackController.cozystackAPIKind` value in the Cozystack controller system Helm chart to "Deployment". ```release-note [controller] Use informer cache instead of the older bespoke implementation and add support for running the Cozystack API as a DaemonSet. ``` Signed-off-by: Timofei Larkin <lllamnyp@gmail.com> |
||
|---|---|---|
| .. | ||
| cozystack-api | ||
| cozystack-assets-server | ||
| cozystack-controller | ||
| kubeovn-plunger | ||
| lineage-controller-webhook | ||