674b3963a7
## What this PR does The lineage-controller-webhook makes a lot of outgoing API calls for every event it handles, contributing to a high API server latency, increasing the number of in-flight requests and generally degrading performance. This patch remedies this by separating the lineage component from the cozystack-controller and deploying it as a separate component on all control-plane nodes. Additionally, a new internal label is introduced to track if a resource has already been handled by the webhook. This label is used to exclude such resources from consideration. Addresses #1513. ### Release note ```release-note [lineage] Break webhook out into a separate daemonset. Reduce unnecessary webhook calls by marking handled resources and excluding them from consideration by the webhook's object selector. ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Standalone Lineage Controller Webhook deployed as its own DaemonSet with a dedicated Helm chart and image build targets. - Dedicated TLS provisioning for the webhook via chart-managed certs. - **Changes** - Main controller no longer hosts webhook endpoints or certificates. - Webhook now excludes already-managed resources to reduce unnecessary invocations. - Platform bundles updated to include the new webhook release. - **Documentation** - Changelog updated to reflect the separation and optimization. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| cozystack-api | ||
| cozystack-assets-server | ||
| cozystack-controller | ||
| kubeovn-plunger | ||
| lineage-controller-webhook | ||