mirror of
https://github.com/cozystack/cozystack.git
synced 2026-10-23 03:27:50 +09:00
Myasnikov Daniil
c2dab12a2e
A restarted capi-operator v0.19.0 drops the create events for the provider Deployments it finds already running (kubernetes-sigs/cluster-api-operator#1031). A provider whose Ready condition went False while the operator was down therefore keeps it until that Deployment changes or the informer resyncs, and the first resync after a restart lands two periods later because the handler registers after the informer has listed. With the 10m default that is about 20 minutes, during which capi-providers-core times out on the CoreProvider and everything depending on it waits; every further operator restart starts the clock again. With a one-minute period the same repro recovered 2m02s after the operator took its lease, against no recovery within 4m26s with the default on the same cluster. A resync replays the cache and, with providers in sync, ends in "No changes detected" and an unchanged condition, so it writes nothing to the API server; the operator logged about 15 lines a minute and used 2m CPU and 26Mi of memory. The upstream chart has no value for the flag, so a package patch that make update reapplies adds one, and a bats test holds the rendered argument. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
15 lines
474 B
Makefile
15 lines
474 B
Makefile
export NAME=capi-operator
|
|
export NAMESPACE=cozy-cluster-api
|
|
export REPO_NAME=capi-operator
|
|
export REPO_URL=https://kubernetes-sigs.github.io/cluster-api-operator
|
|
export CHART_NAME=cluster-api-operator
|
|
export CHART_VERSION=^0.19
|
|
|
|
include ../../../hack/package.mk
|
|
|
|
update: clean capi-operator-update
|
|
rm -rf charts/cluster-api-operator/charts/
|
|
# The upstream chart has no value for --sync-period; values.yaml explains
|
|
# why we set it.
|
|
patch -p1 < patches/sync-period.diff
|