connect to k3d cluster using env variable USE_LOCAL_K3D=true when cluster exists but kubectl config does not #123

Open
opened 2025-08-28 17:43:43 +00:00 by wjro · 0 comments
Owner

kubectl config entry for k3d was delete during a config merge
afterwards the k3d cluster was still running
USE_LOCAL_K3D cargo run -p .... finds the cluster is initialized and marks it as ready
kube config is not updated with a new entry for the harmony k3d cluster and the original kubectl config current-context is not switched during the check to see if the cluster is actually ready
harmony will deploy the app on whichever cluster it is connected to or fail if the context doesnt exist

kubectl config entry for k3d was delete during a config merge afterwards the k3d cluster was still running USE_LOCAL_K3D cargo run -p .... finds the cluster is initialized and marks it as ready kube config is not updated with a new entry for the harmony k3d cluster and the original kubectl config current-context is not switched during the check to see if the cluster is actually ready harmony will deploy the app on whichever cluster it is connected to or fail if the context doesnt exist
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: NationTech/harmony#123
No description provided.