Skip to content

Commit fb1ef59

Browse files
committed
fix(kubernetes): drop undocumented status-beacon annotation from awaiting-etcd ConfigMap
The cozystack.io/status-beacon: "true" annotation had no consumer in the chart, no documented contract, and no convention defined for other charts to follow. It would have become accidental precedent for contributors copying the pattern without understanding it. The ConfigMap itself is self-explanatory: the name <release>-awaiting-etcd, data.status: "awaiting-etcd", and the human-readable message in data.message all surface the same operator signal via kubectl get cm. Drop the annotation; keep the ConfigMap. Assisted-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent 37ecd7b commit fb1ef59

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

‎packages/apps/kubernetes/templates/cluster.yaml‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,8 +106,6 @@ metadata:
106106
app.kubernetes.io/managed-by: {{ .Release.Service }}
107107
app.kubernetes.io/name: kubernetes
108108
app.kubernetes.io/instance: {{ .Release.Name }}
109-
annotations:
110-
cozystack.io/status-beacon: "true"
111109
data:
112110
status: "awaiting-etcd"
113111
message: |

0 commit comments

Comments
 (0)