Skip to content

hack: resolve the kube context before installing micro-VM deps - #1027

Open
Benjamin Elder (BenTheElder) wants to merge 1 commit into
agent-substrate:mainfrom
BenTheElder:hack-pin-kubectl-context
Open

hack: resolve the kube context before installing micro-VM deps#1027
Benjamin Elder (BenTheElder) wants to merge 1 commit into
agent-substrate:mainfrom
BenTheElder:hack-pin-kubectl-context

Conversation

@BenTheElder

Copy link
Copy Markdown
Collaborator

cc Bowei Du (@bowei) yeah ... we need to get these rewritten

It's a good idea to open an issue first for discussion.

  • Tests pass
  • Appropriate changes to documentation are included in the PR

kubectl silently falls back to localhost:8080 when neither --context nor
a kubeconfig current-context is set, so install-microvm-deps.sh died on
the SandboxConfig apply with a bare "connection refused" -- after it had
already assembled the assets and uploaded them to the bucket, which is
the slow part.

Check that a target cluster resolves before doing any of that work, and
print which knob to set. Also thread KUBECTL_CONTEXT into the
install-microvm-deps.sh call in run-microvm-demo.sh, mirroring the
install-ate.sh calls just above it, and give install-ate-kind.sh the
same kind-${KIND_CLUSTER_NAME} default that run-microvm-demo-kind.sh
already has -- it set every other kind-specific variable but left the
context to whatever the kubeconfig happened to point at. An explicit
KUBECTL_CONTEXT still wins everywhere.
@BenTheElder

Copy link
Copy Markdown
Collaborator Author

[trivial rebase on main to pickup CI fixes]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants