Environment
Device and OS: MBP
App version: 0.32.3
Kubernetes distro being used: k3d
Other:
Steps to reproduce
We've seen this consistently on our uds-core package so the steps below reproduce by using that:
zarf p deploy oci://defenseunicorns/uds-k3d:0.4.0 --confirm
zarf init --confirm
zarf p deploy oci://ghcr.io/defenseunicorns/packages/uds/core:0.13.0-registry1 --confirm
Expected result
k3d is deployed with uds-core on top.
Actual Result
Deployment errors out on deploying metrics-server which is a default: true component:
WARNING Retrying (1/3): open
/tmp/zarf-2787421378/images/blobs/sha256/3ef3b57e144bb6cd169eb47bb1e985c863a49d6f15827c8a7467b3b7292e7f07:
no such file or directory
Severity/Priority
Medium - my understanding is that required/default is being refactored so this might not be an issue for long but it is causing issues with current deployments.
Additional Context
We noticed that explicitly selecting the metrics-server component during deploy seems to resolve the issue, as well as pulling then deploying. This seems to exclusively be an issue with a direct OCI deploy.
Environment
Device and OS: MBP
App version: 0.32.3
Kubernetes distro being used: k3d
Other:
Steps to reproduce
We've seen this consistently on our uds-core package so the steps below reproduce by using that:
Expected result
k3d is deployed with uds-core on top.
Actual Result
Deployment errors out on deploying metrics-server which is a
default: truecomponent:Severity/Priority
Medium - my understanding is that required/default is being refactored so this might not be an issue for long but it is causing issues with current deployments.
Additional Context
We noticed that explicitly selecting the
metrics-servercomponent during deploy seems to resolve the issue, as well as pulling then deploying. This seems to exclusively be an issue with a direct OCI deploy.