Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document usage of KIND_CLUSTER_NAME #220

Merged
merged 1 commit into from
Oct 8, 2020
Merged

Document usage of KIND_CLUSTER_NAME #220

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -315,9 +315,13 @@ This would look something like:
kind create cluster

# Deploy to kind w/o registry.
KO_DOCKER_REPO=kind.local ko apply -L -f config/
KO_DOCKER_REPO=kind.local ko apply -f config/
```

If you want to create a `kind` cluster with a non default name, you can set the
`KIND_CLUSTER_NAME` variable to the respective name (which is also supported by
[`kind` itself](https://github.com/kubernetes-sigs/kind/releases/tag/v0.8.0)).

Like with `minikube` above, a caveat of this approach is that it will not work
if your container is configured with `imagePullPolicy: Always` because despite
having the image locally, a pull is performed to ensure we have the latest
Expand Down