zeekayandHanzo AI
ed17bd7898
CI/CD / render (push) Waiting to run
Both declarations pinned 1.2.18; the release is 1.5.49. It is stateless — DISABLE_INDEXER, no database, an emptyDir — so there is no migration between them, only 30 releases of drift. zoo-mainnet goes to zero replicas. Nothing routes to it: no Ingress or route in any namespace names zoo-explorer, and the chain it reads, https://api.zoo.ngo/, answers 404. The chain is down at the source — zood-mv-0 sits Init:0/1 with its staking secret and its startup and genesis ConfigMaps all missing — so two replicas were rendering a chain that does not answer, for nobody. The declaration stays. When zood has its keys the explorer comes back on one line, at the current release rather than a year behind it. Co-authored-by: Hanzo AI <[email protected]>
73 lines
1.9 KiB
YAML
73 lines
1.9 KiB
YAML
# Generated from the live zoo-system/zoo-explorer-explorer Deployment on do-sfo3-zoo-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.kubernetes.io/component: explorer
|
|
app.kubernetes.io/instance: zoo-explorer
|
|
app.kubernetes.io/managed-by: zoo-operator
|
|
app.kubernetes.io/name: zoo-explorer
|
|
containerName: indexer
|
|
image:
|
|
repository: ghcr.io/luxfi/explorer
|
|
tag: 1.5.49
|
|
digest: sha256:907f3d42f84b829d58868a2fff421bdd97868e27a6dc18675412adac1b228461
|
|
pullPolicy: IfNotPresent
|
|
component: explorer
|
|
args:
|
|
- --config=/etc/explorer/chains.yaml
|
|
resources: {}
|
|
volumeMounts:
|
|
- mountPath: /etc/explorer
|
|
name: config
|
|
readOnly: true
|
|
- mountPath: /data
|
|
name: data
|
|
livenessProbe:
|
|
failureThreshold: 3
|
|
httpGet:
|
|
path: /health
|
|
port: 8090
|
|
scheme: HTTP
|
|
initialDelaySeconds: 10
|
|
periodSeconds: 30
|
|
successThreshold: 1
|
|
timeoutSeconds: 1
|
|
readinessProbe:
|
|
failureThreshold: 3
|
|
httpGet:
|
|
path: /health
|
|
port: 8090
|
|
scheme: HTTP
|
|
initialDelaySeconds: 5
|
|
periodSeconds: 10
|
|
successThreshold: 1
|
|
timeoutSeconds: 1
|
|
securityContext:
|
|
readOnlyRootFilesystem: false
|
|
runAsNonRoot: true
|
|
runAsUser: 65532
|
|
ports:
|
|
- containerPort: 8090
|
|
name: http
|
|
volumes:
|
|
- configMap:
|
|
name: zoo-explorer-explorer
|
|
name: config
|
|
- name: data
|
|
rollingUpdate:
|
|
maxSurge: 25%
|
|
maxUnavailable: 25%
|
|
topologySpread:
|
|
enabled: false
|
|
lifecycle: null
|
|
terminationGracePeriodSeconds: 30
|
|
imagePullSecrets: []
|
|
# The immutable spec.selector matches app.kubernetes.io/managed-by=zoo-operator, and the
|
|
# chart's app.labels helper hardcodes `Helm` for that key — so the pod template
|
|
# stops satisfying its own selector and the apply is refused. podLabels are
|
|
# rendered after app.labels, so this restores the one label the selector needs
|
|
# without touching the rest.
|
|
podLabels:
|
|
app.kubernetes.io/managed-by: zoo-operator
|