Files
universe/deploy/lux-system/kube-state-metrics.yaml
T
zeekayandHanzo Dev 425b96f66e the cluster is named, not addressed by a gone account
Every provenance line and manifest still named a DigitalOcean context, and
the ARC values described a pool that died with it. A cluster gets a name
here; the address it answers on belongs to the private record.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 16:15:33 -07:00

69 lines
1.7 KiB
YAML

# Generated from the live lux-system/kube-state-metrics Deployment on lux-k8s
# by hack/live2values.py. Live is the source: a repo of hand-applied
# manifests has unknown currency, the running fleet does not.
replicas: 1
selectorLabels:
app: kube-state-metrics
image:
repository: registry.k8s.io/kube-state-metrics/kube-state-metrics
tag: v2.13.0
pullPolicy: IfNotPresent
partOf: lux-validator-health
labels:
brand: lux
args:
- --port=8080
- --resources=nodes,pods,deployments,daemonsets,statefulsets,replicasets,namespaces,jobs,cronjobs,persistentvolumeclaims
resources:
limits:
cpu: 200m
memory: 160Mi
requests:
cpu: 20m
memory: 48Mi
readinessProbe:
failureThreshold: 3
httpGet:
path: /healthz
port: 8080
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 15
successThreshold: 1
timeoutSeconds: 1
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
ports:
- containerPort: 8080
name: http
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- preference:
matchExpressions:
- key: kubernetes.io/hostname
operator: In
values:
- lux-nodes-3cgkgx
- lux-nodes-3cr32q
- lux-nodes-3csr33
weight: 100
serviceAccountName: kube-state-metrics
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30
imagePullSecrets: []
cd:
# Without this the Application is created and never synced — born
# OutOfSync, never taking ownership. It did not matter while the
# Deployment already existed; it does now that this file has to CREATE it.
automated: false