You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason for this is because Zarf first applies the kustomize build. The kustomize build eliminates the Zarf variables, as they are treated as comments. Thus, the replica property is set to null. This results in the default value of 1 for deployments. While this results in deployments not being scaled, with some CRDs, where the replica property is required, this even breaks packages.
EDIT: The general behaviour of Zarf variables just vanishing can be avoided by quoting the variables. However, this results in typing errors when trying to set actual ints/numbers.
The text was updated successfully, but these errors were encountered:
Environment
Device and OS: Windows 11 / WSL2
App version: v0.41.0
Kubernetes distro being used: EKS / kind
Steps to reproduce
zarf.yaml
manifests/kustomization.yaml
manifests/podinfo.yaml
Expected result
podinfo is running with 3 replicas.
Actual Result
podinfo is running with 1 replica.
The reason for this is because Zarf first applies the kustomize build. The kustomize build eliminates the Zarf variables, as they are treated as comments. Thus, the replica property is set to
null
. This results in the default value of 1 for deployments. While this results in deployments not being scaled, with some CRDs, where the replica property is required, this even breaks packages.EDIT: The general behaviour of Zarf variables just vanishing can be avoided by quoting the variables. However, this results in typing errors when trying to set actual ints/numbers.
The text was updated successfully, but these errors were encountered: