d5d693aa6e
I'm about to refactor the code which includes the Kubernetes support in a way which relies on something vendoring `./cli/context/kubernetes/` in order to trigger the inclusion of support for the Kubernetes endpoint in the final binary. In practice anything which is interested in Kubernetes must import that package (e.g. `./cli/command/context.list` does for the `EndpointFromContext` function). However if it was somehow possible to build without that import then the `KUBERNETES ENDPOINT` column would be mysteriously empty. Out of an abundance of caution add a specific check on the final binary. Signed-off-by: Ian Campbell <ijc@docker.com>
21 lines
390 B
Plaintext
21 lines
390 B
Plaintext
apiVersion: v1
|
|
clusters:
|
|
- cluster:
|
|
certificate-authority-data: dGhlLWNh
|
|
server: https://someserver
|
|
name: test-cluster
|
|
contexts:
|
|
- context:
|
|
cluster: test-cluster
|
|
user: test-user
|
|
namespace: zoinx
|
|
name: test
|
|
current-context: test
|
|
kind: Config
|
|
preferences: {}
|
|
users:
|
|
- name: test-user
|
|
user:
|
|
client-certificate-data: dGhlLWNlcnQ=
|
|
client-key-data: dGhlLWtleQ==
|