defenseunicorns / defenseunicorns/uds-cli

Unable to deploy k3d bundle while kubectl context is set to different architecture

Open
#1,209 3 comments 0 reactions 0 assignees View on GitHub
CLI-v1 possible-bug
Dominant language
Go
Stars
54
Forks
21
Avg merge
2d 15h
Merged PRs (30d)
45

Description

### Environment
Device and OS: MacOS 15.5
App version: v0.27.9
Kubernetes distro being used: EKS for amd64, k3d for arm64, likely irrelevant
Other:

### Steps to reproduce
1. On an arm64 device, set your kubectl context to an amd64 cluster
2. Run `uds deploy k3d-core-slim-dev:0.46.0`
3. It will fail with `failed to validate bundle: arch arm64 does not match cluster arch, [amd64 amd64 amd64 amd64 amd64]`

### Expected result
Since k3d bundle deploys k3d locally to the device, the architecture of the kubectl context cluster is irrelevant and the k3d bundle deploy should deploy

### Visual Proof (screenshots, videos, text, etc)
https://github.com/user-attachments/assets/69f40716-2bdd-4c0b-94fe-053288d3fa38

### Severity/Priority

### Additional Context
While having kubectl context set to amd64 on an arm64 device, I have been unsuccessful in finding a workaround. I have tried the following commands for good measure:
```sh
uds deploy k3d-core-slim-dev:0.46.0
uds deploy k3d-core-slim-dev:0.46.0 -a arm64
UDS_ARCHITECTURE="arm64" uds deploy k3d-core-slim-dev:0.46.0
UDS_ARCHITECTURE="arm64" uds deploy k3d-core-slim-dev:0.46.0 -a arm64
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.