mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-21 20:23:39 +09:00
The tenant kube-apiserver argument list is no longer collapsed into a map keyed by flag name: entries supplied through the control plane spec reach the apiserver verbatim, duplicates included, and the reset that rewrites them from scratch keys on a hash of the list rather than on its length, so a same-count flag swap no longer strands the old flag on the running Deployment. The datastore deletion fix landed upstream verbatim, so its patch no longer applies, and one failing patch fails the whole apply of the directory. The module overlay is obsolete for the opposite reason: this tag already carries golang.org/x/net, golang.org/x/crypto and go.opentelemetry.io/otel/sdk above the versions the overlay forced, so keeping it would downgrade all three. The etcd.deploy override goes with it. The chart's dependency condition is kamaji-etcd.deploy and the subchart is not vendored here, so the key has never selected anything. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
65 lines
2.3 KiB
YAML
65 lines
2.3 KiB
YAML
kamaji:
|
|
# HA-safe default: two replicas serve admission webhooks behind the
|
|
# kamaji-webhook-service Service. --leader-elect is already enabled
|
|
# upstream, so only one replica reconciles tenant control planes — the
|
|
# follower's CPU is fully available for webhook handlers, eliminating the
|
|
# CPU contention that pushes p99 admission latency from ~10ms (kamaji
|
|
# handler) up to ~90ms (apiserver-observed) on single-replica deployments.
|
|
replicaCount: 2
|
|
# Drop the telemetry handler and its admission webhook. With
|
|
# telemetry.disabled=true, the controller is started with
|
|
# --disable-telemetry AND the corresponding webhook entry is omitted
|
|
# from the ValidatingWebhookConfiguration (see patches/1.diff), so the
|
|
# apiserver no longer pays a round-trip to a no-op handler on every
|
|
# TenantControlPlane CREATE/UPDATE/DELETE.
|
|
telemetry:
|
|
disabled: true
|
|
# Soft anti-affinity: spread the kamaji controller replicas across nodes
|
|
# when possible. preferredDuringScheduling means single-node clusters
|
|
# still schedule both pods (just colocated, which is acceptable).
|
|
affinity:
|
|
podAntiAffinity:
|
|
preferredDuringSchedulingIgnoredDuringExecution:
|
|
- weight: 100
|
|
podAffinityTerm:
|
|
labelSelector:
|
|
matchLabels:
|
|
app.kubernetes.io/name: kamaji
|
|
topologyKey: kubernetes.io/hostname
|
|
image:
|
|
pullPolicy: IfNotPresent
|
|
tag: v1.6.0@sha256:7f7751b3d01b256621a131c217fc90464cd51d3d07a6d870c3d8f28784745293
|
|
repository: ghcr.io/cozystack/cozystack/kamaji
|
|
resources:
|
|
limits:
|
|
cpu: 200m
|
|
memory: 512Mi
|
|
requests:
|
|
cpu: 100m
|
|
memory: 256Mi
|
|
startupProbe:
|
|
httpGet:
|
|
path: /healthz
|
|
port: healthcheck
|
|
initialDelaySeconds: 5
|
|
periodSeconds: 5
|
|
timeoutSeconds: 3
|
|
successThreshold: 1
|
|
failureThreshold: 12
|
|
livenessProbe:
|
|
httpGet:
|
|
path: /healthz
|
|
port: healthcheck
|
|
initialDelaySeconds: 30
|
|
periodSeconds: 20
|
|
timeoutSeconds: 1
|
|
readinessProbe:
|
|
httpGet:
|
|
path: /readyz
|
|
port: healthcheck
|
|
initialDelaySeconds: 30
|
|
periodSeconds: 10
|
|
timeoutSeconds: 1
|
|
extraArgs:
|
|
- --migrate-image=ghcr.io/cozystack/cozystack/kamaji:v1.6.0@sha256:7f7751b3d01b256621a131c217fc90464cd51d3d07a6d870c3d8f28784745293
|