DockerCLI/cli/command/context/testdata/test-kubeconfig

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: dGhlLWNh
    server: https://someserver.example.com
  name: test-cluster
contexts:
- context:
    cluster: test-cluster
    user: test-user
  name: test
current-context: test
kind: Config
preferences: {}
users:
- name: test-user
  user:
    client-certificate-data: dGhlLWNlcnQ=
    client-key-data: dGhlLWtleQ==
Fast Context Switch: commands Signed-off-by: Simon Ferquel <simon.ferquel@docker.com> 2018-11-09 09:10:41 -05:00			`apiVersion: v1`
			`clusters:`
			`- cluster:`
			`certificate-authority-data: dGhlLWNh`
Use designated test domains (RFC2606) in tests Some tests were using domain names that were intended to be "fake", but are actually registered domain names (such as mycorp.com). Even though we were not actually making connections to these domains, it's better to use domains that are designated for testing/examples in RFC2606: https://tools.ietf.org/html/rfc2606 Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit f3886f354a918d61933d648db10b128a5f6401b1) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 2021-04-30 03:31:41 -04:00			`server: https://someserver.example.com`
Fast Context Switch: commands Signed-off-by: Simon Ferquel <simon.ferquel@docker.com> 2018-11-09 09:10:41 -05:00			`name: test-cluster`
			`contexts:`
			`- context:`
			`cluster: test-cluster`
			`user: test-user`
			`name: test`
			`current-context: test`
			`kind: Config`
			`preferences: {}`
			`users:`
			`- name: test-user`
			`user:`
			`client-certificate-data: dGhlLWNlcnQ=`
			`client-key-data: dGhlLWtleQ==`