Skip to content

Commit 67ae3de

Browse files
authored
Merge pull request #39656 from dipesh-rawat/change-scratch-term
Changed the occurrence of scratch to test
2 parents fe254a7 + 2afb7d7 commit 67ae3de

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -41,12 +41,12 @@ cluster's API server.
4141

4242
## Define clusters, users, and contexts
4343

44-
Suppose you have two clusters, one for development work and one for scratch work.
44+
Suppose you have two clusters, one for development work and one for test work.
4545
In the `development` cluster, your frontend developers work in a namespace called `frontend`,
46-
and your storage developers work in a namespace called `storage`. In your `scratch` cluster,
46+
and your storage developers work in a namespace called `storage`. In your `test` cluster,
4747
developers work in the default namespace, or they create auxiliary namespaces as they
4848
see fit. Access to the development cluster requires authentication by certificate. Access
49-
to the scratch cluster requires authentication by username and password.
49+
to the test cluster requires authentication by username and password.
5050

5151
Create a directory named `config-exercise`. In your
5252
`config-exercise` directory, create a file named `config-demo` with this content:
@@ -60,7 +60,7 @@ clusters:
6060
- cluster:
6161
name: development
6262
- cluster:
63-
name: scratch
63+
name: test
6464

6565
users:
6666
- name: developer
@@ -72,7 +72,7 @@ contexts:
7272
- context:
7373
name: dev-storage
7474
- context:
75-
name: exp-scratch
75+
name: exp-test
7676
```
7777
7878
A configuration file describes clusters, users, and contexts. Your `config-demo` file
@@ -83,7 +83,7 @@ your configuration file:
8383

8484
```shell
8585
kubectl config --kubeconfig=config-demo set-cluster development --server=https://1.2.3.4 --certificate-authority=fake-ca-file
86-
kubectl config --kubeconfig=config-demo set-cluster scratch --server=https://5.6.7.8 --insecure-skip-tls-verify
86+
kubectl config --kubeconfig=config-demo set-cluster test --server=https://5.6.7.8 --insecure-skip-tls-verify
8787
```
8888

8989
Add user details to your configuration file:
@@ -108,7 +108,7 @@ Add context details to your configuration file:
108108
```shell
109109
kubectl config --kubeconfig=config-demo set-context dev-frontend --cluster=development --namespace=frontend --user=developer
110110
kubectl config --kubeconfig=config-demo set-context dev-storage --cluster=development --namespace=storage --user=developer
111-
kubectl config --kubeconfig=config-demo set-context exp-scratch --cluster=scratch --namespace=default --user=experimenter
111+
kubectl config --kubeconfig=config-demo set-context exp-test --cluster=test --namespace=default --user=experimenter
112112
```
113113

114114
Open your `config-demo` file to see the added details. As an alternative to opening the
@@ -130,7 +130,7 @@ clusters:
130130
- cluster:
131131
insecure-skip-tls-verify: true
132132
server: https://5.6.7.8
133-
name: scratch
133+
name: test
134134
contexts:
135135
- context:
136136
cluster: development
@@ -143,10 +143,10 @@ contexts:
143143
user: developer
144144
name: dev-storage
145145
- context:
146-
cluster: scratch
146+
cluster: test
147147
namespace: default
148148
user: experimenter
149-
name: exp-scratch
149+
name: exp-test
150150
current-context: ""
151151
kind: Config
152152
preferences: {}
@@ -220,19 +220,19 @@ users:
220220
client-key: fake-key-file
221221
```
222222

223-
Now suppose you want to work for a while in the scratch cluster.
223+
Now suppose you want to work for a while in the test cluster.
224224

225-
Change the current context to `exp-scratch`:
225+
Change the current context to `exp-test`:
226226

227227
```shell
228-
kubectl config --kubeconfig=config-demo use-context exp-scratch
228+
kubectl config --kubeconfig=config-demo use-context exp-test
229229
```
230230

231231
Now any `kubectl` command you give will apply to the default namespace of
232-
the `scratch` cluster. And the command will use the credentials of the user
233-
listed in the `exp-scratch` context.
232+
the `test` cluster. And the command will use the credentials of the user
233+
listed in the `exp-test` context.
234234

235-
View configuration associated with the new current context, `exp-scratch`.
235+
View configuration associated with the new current context, `exp-test`.
236236

237237
```shell
238238
kubectl config --kubeconfig=config-demo view --minify
@@ -338,10 +338,10 @@ contexts:
338338
user: developer
339339
name: dev-storage
340340
- context:
341-
cluster: scratch
341+
cluster: test
342342
namespace: default
343343
user: experimenter
344-
name: exp-scratch
344+
name: exp-test
345345
```
346346

347347
For more information about how kubeconfig files are merged, see

0 commit comments

Comments
 (0)