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
Device and OS: M1 Mac
App version: v0.25.0
Kubernetes distro being used: k3d (k3s in docker)
Other: This is agnostic to device/OS and k8s distro. The information about package and cluster architecture just need to be swapped when an application package's architecture doesn't match a cluster's architecture.
Steps to reproduce
Create a cluster. In this case, a k3d cluster on an M1 Mac:
k3d cluster create
The architecture of the nodes is arm64.
Initialize the cluster with an arm64 init package:
zarf init
Attempt to deploy a zarf package with amd64 architecture to the arm64 cluster:
zarf package deploy zarf-package-cool-app-amd64
Expected result
The deployment fails because the architectures do not match, and zarf tells me why.
Actual Result
The deployment fails because the architectures do not match, and zarf tells me why, but prints out backwards/incorrect architecture data in the error message.
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Unsure.
The text was updated successfully, but these errors were encountered:
Environment
Device and OS: M1 Mac
App version: v0.25.0
Kubernetes distro being used: k3d (k3s in docker)
Other: This is agnostic to device/OS and k8s distro. The information about package and cluster architecture just need to be swapped when an application package's architecture doesn't match a cluster's architecture.
Steps to reproduce
The architecture of the nodes is
arm64
.arm64
init package:amd64
architecture to thearm64
cluster:Expected result
The deployment fails because the architectures do not match, and zarf tells me why.
Actual Result
The deployment fails because the architectures do not match, and zarf tells me why, but prints out backwards/incorrect architecture data in the error message.
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Unsure.
The text was updated successfully, but these errors were encountered: