Drop the zoo-computer architecture pin
The pin rested on an arm64 pull error, "no match for platform in manifest". On the amd64 node the same digest reports plainly: not found. zoo-mainnet has no ghcr-luxfi secret, the one the values file names, so the private repository answers every request as a miss on both nodes and the earlier message says nothing about which platforms are published. Provision the pull secret first; the manifest can then be read and the architecture, if it needs constraining, constrained against evidence. Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
@@ -49,10 +49,6 @@ ports:
|
||||
- containerPort: 3000
|
||||
imagePullSecrets:
|
||||
- name: ghcr-luxfi
|
||||
# ghcr.io/zooai/computer publishes amd64 only; on the arm64 node the pull
|
||||
# fails with "no match for platform in manifest".
|
||||
nodeSelector:
|
||||
kubernetes.io/arch: amd64
|
||||
rollingUpdate:
|
||||
maxSurge: 25%
|
||||
maxUnavailable: 25%
|
||||
|
||||
Reference in New Issue
Block a user