Skip to content

Commit 447f1dc

Browse files
myasnikovdaniilmyasnikovdaniil
committed
fix(kafka): place enableServiceLinks under template.pod, not a phantom .spec
Same class of bug as the foundationdb misplaced-field fixes. The kafka chart had: entityOperator: template: pod: metadata: { labels: { ... } } spec: ← child of template, not of pod enableServiceLinks: false The Strimzi Kafka CRD's `entityOperator.template` has no `spec` key. `enableServiceLinks` is a direct field of `template.pod` (alongside metadata, affinity, tolerations, etc.). Flux v2.7's permissive client-side patch silently dropped the misplaced field; v2.8's strict Server-Side Apply rejects: failed to create typed patch object (Kind=Kafka): .spec.entityOperator.template.spec: field not declared in schema Move `enableServiceLinks` under `template.pod` where the operator actually reads it, and fix the inconsistent metadata.labels indentation (was 9/11 spaces instead of 10/12) while we're here. Assisted-By: Claude <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 4fcd546 commit 447f1dc

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

‎packages/apps/kafka/templates/kafka.yaml‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,9 +84,13 @@ spec:
8484
topicOperator: {}
8585
userOperator: {}
8686
template:
87+
# `pod` accepts metadata + a flat set of pod-spec fields
88+
# (enableServiceLinks, securityContext, affinity, …) directly.
89+
# The previous file nested enableServiceLinks under a phantom
90+
# `template.spec` key — Flux v2.7 dropped it silently, v2.8 SSA
91+
# rejects it with "field not declared in schema".
8792
pod:
8893
metadata:
89-
labels:
90-
policy.cozystack.io/allow-to-apiserver: "true"
91-
spec:
94+
labels:
95+
policy.cozystack.io/allow-to-apiserver: "true"
9296
enableServiceLinks: false

0 commit comments

Comments
 (0)