This repository was archived by the owner on Jul 9, 2025. It is now read-only.
Document new EKS_K8S_PROVIDER configuration #1441
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We are currently making some changes, to replace the implicit switch between the
k3s
andlocal
EKS K8S providers, which lead to a lot of confusion.In the future, the switch is made purely by the
EKS_K8S_PROVIDER
configuration variable, the mounting of a kubeconfig alone will no longer suffice to switch to thelocal
provider.Also, we stop automatically mounting the kube config at
~/.kube/config
from the host into the container.Changes
EKS_K8S_PROVIDER
config variable