Closed mjnagel closed 1 month ago
N/A - not environment specific, but encountered on RKE2.
Package
Deployment should fail if Package CR is not ready.
Since helm/zarf do not wait on the Package, and there is no action in the zarf.yaml to wait on it, it's status is ignored for the deployment.
Low/Medium
In uds-core we added onDeploy.after actions to most packages to validate they are fully healthy before proceeding, example - https://github.com/defenseunicorns/uds-core/blob/main/src/grafana/common/zarf.yaml#L21-L31. Unsure, but expect this is an issue on other SWF repos as well.
Environment
N/A - not environment specific, but encountered on RKE2.
Steps to reproduce
Packageconfiguration (example: add an erroneous client scope)Expected result
Deployment should fail if
PackageCR is not ready.Actual Result
Since helm/zarf do not wait on the
Package, and there is no action in the zarf.yaml to wait on it, it's status is ignored for the deployment.Severity/Priority
Low/Medium
Additional Context
In uds-core we added onDeploy.after actions to most packages to validate they are fully healthy before proceeding, example - https://github.com/defenseunicorns/uds-core/blob/main/src/grafana/common/zarf.yaml#L21-L31. Unsure, but expect this is an issue on other SWF repos as well.