Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed because of a cast error
Error code: DatasetGenerationCastError
Exception: DatasetGenerationCastError
Message: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 7 new columns ({'total_words', 'docs_with_code', 'total_documents', 'subcategories', 'code_languages', 'categories', 'avg_words_per_doc'}) and 7 missing columns ({'type', 'completion', 'language', 'id', 'source', 'prompt', 'context'}).
This happened while the json dataset builder was generating data using
hf://datasets/Masterbtc/Kubernetes_documentation/dataset_statistics.json (at revision 3fc8c6797c94bec1206ce918c1e0a332369ea0ce)
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback: Traceback (most recent call last):
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1831, in _prepare_split_single
writer.write_table(table)
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/arrow_writer.py", line 644, in write_table
pa_table = table_cast(pa_table, self._schema)
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2272, in table_cast
return cast_table_to_schema(table, schema)
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2218, in cast_table_to_schema
raise CastError(
datasets.table.CastError: Couldn't cast
total_documents: int64
total_words: int64
categories: struct<reference: struct<count: int64, words: int64>, tasks: struct<count: int64, words: int64>, other: struct<count: int64, words: int64>, concepts: struct<count: int64, words: int64>, tutorials: struct<count: int64, words: int64>>
child 0, reference: struct<count: int64, words: int64>
child 0, count: int64
child 1, words: int64
child 1, tasks: struct<count: int64, words: int64>
child 0, count: int64
child 1, words: int64
child 2, other: struct<count: int64, words: int64>
child 0, count: int64
child 1, words: int64
child 3, concepts: struct<count: int64, words: int64>
child 0, count: int64
child 1, words: int64
child 4, tutorials: struct<count: int64, words: int64>
child 0, count: int64
child 1, words: int64
subcategories: struct<general-reference: struct<count: int64, words: int64>, manage-clusters: struct<count: int64, words: int64>, configure-pods-containers: struct<count: int64, words: int64>, uncategorized: struct<count: int64, words: int64>, overview-architecture: struct<count: int64, words: int64>, api-reference: struct<count: int64, words: int64>, cli-reference: struct<count: int64, words: int64>, general-tasks: struct<count: int64, words: int64>, services-networking: struct<count: int64, words: int64>, cluster-administration: struct<count: int64, words: int64>, storage: struct<count: int64, words: int64>, run-jobs: struct<count: int64, words: i
...
t64, liquid: int64, docker: int64, sh: int64, html: int64, cpp: int64, cel: int64, systemd: int64, conf: int64, go-html-template: int64, go-text-template: int64, markdown: int64, zsh: int64, toml: int64, patch: int64, hexdump: int64, diff: int64, golang: int64, java: int64, csharp: int64, javascript: int64, haskell: int64, promql: int64, http: int64, ini: int64, proto: int64, PowerShell: int64, gRPC: int64, env: int64, output: int64>
child 0, text: int64
child 1, bash: int64
child 2, none: int64
child 3, shell: int64
child 4, cmd: int64
child 5, yaml: int64
child 6, json: int64
child 7, console: int64
child 8, go: int64
child 9, python: int64
child 10, powershell: int64
child 11, liquid: int64
child 12, docker: int64
child 13, sh: int64
child 14, html: int64
child 15, cpp: int64
child 16, cel: int64
child 17, systemd: int64
child 18, conf: int64
child 19, go-html-template: int64
child 20, go-text-template: int64
child 21, markdown: int64
child 22, zsh: int64
child 23, toml: int64
child 24, patch: int64
child 25, hexdump: int64
child 26, diff: int64
child 27, golang: int64
child 28, java: int64
child 29, csharp: int64
child 30, javascript: int64
child 31, haskell: int64
child 32, promql: int64
child 33, http: int64
child 34, ini: int64
child 35, proto: int64
child 36, PowerShell: int64
child 37, gRPC: int64
child 38, env: int64
child 39, output: int64
avg_words_per_doc: double
docs_with_code: int64
to
{'prompt': Value('string'), 'completion': Value('string'), 'language': Value('string'), 'type': Value('string'), 'context': Value('string'), 'source': Value('string'), 'id': Value('string')}
because column names don't match
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1456, in compute_config_parquet_and_info_response
parquet_operations = convert_to_parquet(builder)
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1055, in convert_to_parquet
builder.download_and_prepare(
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 894, in download_and_prepare
self._download_and_prepare(
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 970, in _download_and_prepare
self._prepare_split(split_generator, **prepare_split_kwargs)
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1702, in _prepare_split
for job_id, done, content in self._prepare_split_single(
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1833, in _prepare_split_single
raise DatasetGenerationCastError.from_cast_error(
datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 7 new columns ({'total_words', 'docs_with_code', 'total_documents', 'subcategories', 'code_languages', 'categories', 'avg_words_per_doc'}) and 7 missing columns ({'type', 'completion', 'language', 'id', 'source', 'prompt', 'context'}).
This happened while the json dataset builder was generating data using
hf://datasets/Masterbtc/Kubernetes_documentation/dataset_statistics.json (at revision 3fc8c6797c94bec1206ce918c1e0a332369ea0ce)
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
prompt
string | completion
string | language
string | type
string | context
string | source
string | id
string |
|---|---|---|---|---|---|---|
Explain this text code:
pod-security.kubernetes.io/enforce-policy: restricted:latest
|
This text code Audit Annotations | Value must be privileged:<version>, baseline:<version>, restricted:<version> which correspond to Pod Security Standard levels accompanied by a version which must be latest or a valid Kubernetes versio
|
text
|
code-example_explanation
|
Audit Annotations | Value must be privileged:<version>, baseline:<version>, restricted:<version> which correspond to Pod Security Standard levels accompanied by a version which must be latest or a valid Kubernetes versio
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_0
|
Explain this text code:
pod-security.kubernetes.io/audit-violations: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "example" must set securityContext.allowPrivilegeEscalation=false), ...
|
This text code Audit Annotations | Value details an audit policy violation, it contains the Pod Security Standard level that was transgressed as well as the specific policies on the fields that were violated from the PodSecurity enforc
|
text
|
code-example_explanation
|
Audit Annotations | Value details an audit policy violation, it contains the Pod Security Standard level that was transgressed as well as the specific policies on the fields that were violated from the PodSecurity enforc
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_1
|
Explain this text code:
apiserver.latency.k8s.io/decode-response-object: "450.6649ns"
|
This text code Audit Annotations | This annotation records the time taken to decode the response received from the storage layer (etcd)
|
text
|
code-example_explanation
|
Audit Annotations | This annotation records the time taken to decode the response received from the storage layer (etcd)
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_2
|
Explain this text code:
authorization.k8s.io/reason: "Human-readable reason for the decision"
|
This text code Audit Annotations | This annotation gives reason for the decision in Kubernetes audit logs.
|
text
|
code-example_explanation
|
Audit Annotations | This annotation gives reason for the decision in Kubernetes audit logs.
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_3
|
Explain this text code:
missing-san.invalid-cert.kubernetes.io/example-svc.example-namespace.svc: "relies on a legacy Common Name field instead of the SAN extension for subject validation"
|
This text code Audit Annotations | Used by Kubernetes version v1.24 and later
|
text
|
code-example_explanation
|
Audit Annotations | Used by Kubernetes version v1.24 and later
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_4
|
Explain this text code:
insecure-sha1.invalid-cert.kubernetes.io/example-svc.example-namespace.svc: "uses an insecure SHA-1 signature"
|
This text code Audit Annotations | Used by Kubernetes version v1.24 and later
|
text
|
code-example_explanation
|
Audit Annotations | Used by Kubernetes version v1.24 and later
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_5
|
Explain this text code:
validation.policy.admission.k8s.io/validation_failure: '[{"message": "Invalid value", {"policy": "policy.example.com", {"binding": "policybinding.example.com", {"expressionIndex": "1", {"validationActions": ["Audit"]}]'
|
This text code Audit Annotations | Used by Kubernetes version v1.27 and later.
|
text
|
code-example_explanation
|
Audit Annotations | Used by Kubernetes version v1.27 and later.
|
https://kubernetes.io/docs/reference/labels-annotations-taints/audit-annotations/
|
k8s_00000_code_explain_6
|
Complete this text code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 10s
|
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 6s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim3 manual 3s
|
text
|
code-example
|
Change the Reclaim Policy of a PersistentVolume | This list also includes the name of the claims that are bound to each volume for easier identification of dynamically provisioned volumes.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_completion_7
|
Explain this text code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 10s
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 6s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim3 manual 3s
|
This text code Change the Reclaim Policy of a PersistentVolume | This list also includes the name of the claims that are bound to each volume for easier identification of dynamically provisioned volumes.
|
text
|
code-example_explanation
|
Change the Reclaim Policy of a PersistentVolume | This list also includes the name of the claims that are bound to each volume for easier identification of dynamically provisioned volumes.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_8
|
Explain this bash code:
kubectl patch pv <your-pv-name> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'
|
This bash code Change the Reclaim Policy of a PersistentVolume | where <your-pv-name> is the name of your chosen PersistentVolume.
|
bash
|
kubectl-command_explanation
|
Change the Reclaim Policy of a PersistentVolume | where <your-pv-name> is the name of your chosen PersistentVolume.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_9
|
Explain this bash code:
kubectl patch pv <your-pv-name> -p "{\"spec\":{\"persistentVolumeReclaimPolicy\":\"Retain\"}}"
|
This bash code Change the Reclaim Policy of a PersistentVolume | Verify that your chosen PersistentVolume has the right policy:
|
bash
|
kubectl-command_explanation
|
Change the Reclaim Policy of a PersistentVolume | Verify that your chosen PersistentVolume has the right policy:
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_10
|
Complete this text code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 40s
|
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 36s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Retain Bound default/claim3 manual 33s
|
text
|
code-example
|
Change the Reclaim Policy of a PersistentVolume | In the preceding output, you can see that the volume bound to claim default/claim3 has reclaim policy Retain. It will not be automatically deleted when a user deletes claim default/claim3.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_completion_11
|
Explain this text code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 40s
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 36s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Retain Bound default/claim3 manual 33s
|
This text code Change the Reclaim Policy of a PersistentVolume | In the preceding output, you can see that the volume bound to claim default/claim3 has reclaim policy Retain. It will not be automatically deleted when a user deletes claim default/claim3.
|
text
|
code-example_explanation
|
Change the Reclaim Policy of a PersistentVolume | In the preceding output, you can see that the volume bound to claim default/claim3 has reclaim policy Retain. It will not be automatically deleted when a user deletes claim default/claim3.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_12
|
Complete this none code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 10s
|
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 6s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim3 manual 3s
|
none
|
code-example
|
Change the Reclaim Policy of a PersistentVolume | This list also includes the name of the claims that are bound to each volume for easier identification of dynamically provisioned volumes.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_completion_13
|
Explain this none code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 10s
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 6s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim3 manual 3s
|
This none code Change the Reclaim Policy of a PersistentVolume | This list also includes the name of the claims that are bound to each volume for easier identification of dynamically provisioned volumes.
|
none
|
code-example_explanation
|
Change the Reclaim Policy of a PersistentVolume | This list also includes the name of the claims that are bound to each volume for easier identification of dynamically provisioned volumes.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_14
|
Explain this shell code:
kubectl patch pv <your-pv-name> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'
|
This shell code Change the Reclaim Policy of a PersistentVolume | where <your-pv-name> is the name of your chosen PersistentVolume.
|
shell
|
code-example_explanation
|
Change the Reclaim Policy of a PersistentVolume | where <your-pv-name> is the name of your chosen PersistentVolume.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_15
|
Explain this cmd code:
kubectl patch pv <your-pv-name> -p "{\"spec\":{\"persistentVolumeReclaimPolicy\":\"Retain\"}}"
|
This cmd code Change the Reclaim Policy of a PersistentVolume | Verify that your chosen PersistentVolume has the right policy:
|
cmd
|
code-example_explanation
|
Change the Reclaim Policy of a PersistentVolume | Verify that your chosen PersistentVolume has the right policy:
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_16
|
Complete this none code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 40s
|
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 36s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Retain Bound default/claim3 manual 33s
|
none
|
code-example
|
Change the Reclaim Policy of a PersistentVolume | In the preceding output, you can see that the volume bound to claim default/claim3 has reclaim policy Retain. It will not be automatically deleted when a user deletes claim default/claim3.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_completion_17
|
Explain this none code:
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim1 manual 40s
pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Delete Bound default/claim2 manual 36s
pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94 4Gi RWO Retain Bound default/claim3 manual 33s
|
This none code Change the Reclaim Policy of a PersistentVolume | In the preceding output, you can see that the volume bound to claim default/claim3 has reclaim policy Retain. It will not be automatically deleted when a user deletes claim default/claim3.
|
none
|
code-example_explanation
|
Change the Reclaim Policy of a PersistentVolume | In the preceding output, you can see that the volume bound to claim default/claim3 has reclaim policy Retain. It will not be automatically deleted when a user deletes claim default/claim3.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_18
|
Explain this bash code:
kubectl patch pv <your-pv-name> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'
|
This bash code Change the Reclaim Policy of a PersistentVolume | where <your-pv-name> is the name of your chosen PersistentVolume.
|
bash
|
kubectl-command_explanation
|
Change the Reclaim Policy of a PersistentVolume | where <your-pv-name> is the name of your chosen PersistentVolume.
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_19
|
Explain this bash code:
kubectl patch pv <your-pv-name> -p "{\"spec\":{\"persistentVolumeReclaimPolicy\":\"Retain\"}}"
|
This bash code Change the Reclaim Policy of a PersistentVolume | Verify that your chosen PersistentVolume has the right policy:
|
bash
|
kubectl-command_explanation
|
Change the Reclaim Policy of a PersistentVolume | Verify that your chosen PersistentVolume has the right policy:
|
https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/
|
k8s_00001_code_explain_20
|
Complete this yaml code:
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
|
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
yaml
|
pod-definition
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_completion_21
|
Explain this yaml code:
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
This yaml code Use a User Namespace With a Pod | Create the pod on your cluster:
|
yaml
|
pod-definition_explanation
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_22
|
Explain this bash code:
kubectl apply -f https://k8s.io/examples/pods/user-namespaces-stateless.yaml
|
This bash code Use a User Namespace With a Pod | Exec into the pod and run readlink /proc/self/ns/user:
|
bash
|
kubectl-command_explanation
|
Use a User Namespace With a Pod | Exec into the pod and run readlink /proc/self/ns/user:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_23
|
Complete this yaml code:
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
|
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
yaml
|
pod-definition
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_completion_24
|
Explain this yaml code:
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
This yaml code Use a User Namespace With a Pod | Create the pod on your cluster:
|
yaml
|
pod-definition_explanation
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_25
|
Explain this shell code:
kubectl apply -f https://k8s.io/examples/pods/user-namespaces-stateless.yaml
|
This shell code Use a User Namespace With a Pod | Exec into the pod and run readlink /proc/self/ns/user:
|
shell
|
code-example_explanation
|
Use a User Namespace With a Pod | Exec into the pod and run readlink /proc/self/ns/user:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_26
|
Complete this yaml code:
pods/user-namespaces-stateless.yaml
apiVersion: v1
kind: Pod
metadata:
name: userns
|
spec:
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
yaml
|
pod-definition
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_completion_27
|
Explain this yaml code:
pods/user-namespaces-stateless.yaml
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
This yaml code Use a User Namespace With a Pod | Create the pod on your cluster:
|
yaml
|
pod-definition_explanation
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_28
|
Complete this yaml code:
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
|
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
yaml
|
pod-definition
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_completion_29
|
Explain this yaml code:
apiVersion: v1
kind: Pod
metadata:
name: userns
spec:
hostUsers: false
containers:
- name: shell
command: ["sleep", "infinity"]
image: debian
|
This yaml code Use a User Namespace With a Pod | Create the pod on your cluster:
|
yaml
|
pod-definition_explanation
|
Use a User Namespace With a Pod | Create the pod on your cluster:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_30
|
Explain this bash code:
kubectl apply -f https://k8s.io/examples/pods/user-namespaces-stateless.yaml
|
This bash code Use a User Namespace With a Pod | Exec into the pod and run readlink /proc/self/ns/user:
|
bash
|
kubectl-command_explanation
|
Use a User Namespace With a Pod | Exec into the pod and run readlink /proc/self/ns/user:
|
https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
|
k8s_00002_code_explain_31
|
Complete this text code:
preflight Run pre-flight checks
certs Certificate generation
/ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
/apiserver Generate the certificate for serving the Kubernetes API
/apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
/front-proxy-ca Generate the self-signed CA to provision identities for front proxy
/front-proxy-client Generate the certificate for the front proxy client
/etcd-ca Generate the self-signed CA to provision identities for etcd
/etcd-server Generate the certificate for serving etcd
/etcd-peer Generate the certificate for etcd nodes to communicate with each other
/etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
/apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
/sa Generate a private key for signing service account tokens along with its public key
kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
/admin Generate a kubeconfig file for the admin to use and for kubeadm itself
/super-admin Generate a kubeconfig file for the super-admin
/kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
/controller-manager Generate a kubeconfig file for the controller manager to use
/scheduler Generate a kubeconfig file for the scheduler to use
|
etcd Generate static Pod manifest file for local etcd
/local Generate the static Pod manifest file for a local, single-node local etcd instance
control-plane Generate all static Pod manifest files necessary to establish the control plane
/apiserver Generates the kube-apiserver static Pod manifest
/controller-manager Generates the kube-controller-manager static Pod manifest
/scheduler Generates the kube-scheduler static Pod manifest
kubelet-start Write kubelet settings and (re)start the kubelet
wait-control-plane Wait for the control plane to start
upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
/kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
/kubelet Upload the kubelet component config to a ConfigMap
upload-certs Upload certificates to kubeadm-certs
mark-control-plane Mark a node as a control-plane
bootstrap-token Generates bootstrap tokens used to join a node to a cluster
kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap
/enable-client-cert-rotation Enable kubelet client certificate rotation
addon Install required addons for passing conformance tests
/coredns Install the CoreDNS addon to a Kubernetes cluster
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster
show-join-command Show the join command for control-plane and worker node
|
text
|
code-example
|
kubeadm init | The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_completion_32
|
Explain this text code:
preflight Run pre-flight checks
certs Certificate generation
/ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
/apiserver Generate the certificate for serving the Kubernetes API
/apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
/front-proxy-ca Generate the self-signed CA to provision identities for front proxy
/front-proxy-client Generate the certificate for the front proxy client
/etcd-ca Generate the self-signed CA to provision identities for etcd
/etcd-server Generate the certificate for serving etcd
/etcd-peer Generate the certificate for etcd nodes to communicate with each other
/etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
/apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
/sa Generate a private key for signing service account tokens along with its public key
kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
/admin Generate a kubeconfig file for the admin to use and for kubeadm itself
/super-admin Generate a kubeconfig file for the super-admin
/kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
/controller-manager Generate a kubeconfig file for the controller manager to use
/scheduler Generate a kubeconfig file for the scheduler to use
etcd Generate static Pod manifest file for local etcd
/local Generate the static Pod manifest file for a local, single-node local etcd instance
control-plane Generate all static Pod manifest files necessary to establish the control plane
/apiserver Generates the kube-apiserver static Pod manifest
/controller-manager Generates the kube-controller-manager static Pod manifest
/scheduler Generates the kube-scheduler static Pod manifest
kubelet-start Write kubelet settings and (re)start the kubelet
wait-control-plane Wait for the control plane to start
upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
/kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
/kubelet Upload the kubelet component config to a ConfigMap
upload-certs Upload certificates to kubeadm-certs
mark-control-plane Mark a node as a control-plane
bootstrap-token Generates bootstrap tokens used to join a node to a cluster
kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap
/enable-client-cert-rotation Enable kubelet client certificate rotation
addon Install required addons for passing conformance tests
/coredns Install the CoreDNS addon to a Kubernetes cluster
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster
show-join-command Show the join command for control-plane and worker node
|
This text code kubeadm init | The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
text
|
code-example_explanation
|
kubeadm init | The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_33
|
Explain this text code:
sudo kubeadm init phase control-plane controller-manager --help
|
This text code kubeadm init | You can also use --help to see the list of sub-phases for a certain parent phase:
|
text
|
code-example_explanation
|
kubeadm init | You can also use --help to see the list of sub-phases for a certain parent phase:
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_34
|
Complete this text code:
sudo kubeadm init phase control-plane all --config=configfile.yaml
sudo kubeadm init phase etcd local --config=configfile.yaml
|
# you can now modify the control plane and etcd manifest files
sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
|
text
|
code-example
|
kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_completion_35
|
Explain this text code:
sudo kubeadm init phase control-plane all --config=configfile.yaml
sudo kubeadm init phase etcd local --config=configfile.yaml
# you can now modify the control plane and etcd manifest files
sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
|
This text code kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
text
|
code-example_explanation
|
kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_36
|
Explain this text code:
kubeadm config images list
kubeadm config images pull
|
This text code kubeadm init | You can pass --config to the above commands with a kubeadm configuration file to control the kubernetesVersion and imageRepository fields.
|
text
|
code-example_explanation
|
kubeadm init | You can pass --config to the above commands with a kubeadm configuration file to control the kubernetesVersion and imageRepository fields.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_37
|
Explain this text code:
kubeadm init phase upload-certs --upload-certs --config=SOME_YAML_FILE
|
This text code kubeadm init | If a predefined certificate key is not passed to kubeadm init and kubeadm init phase upload-certs a new key will be generated automatically.
|
text
|
code-example_explanation
|
kubeadm init | If a predefined certificate key is not passed to kubeadm init and kubeadm init phase upload-certs a new key will be generated automatically.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_38
|
Complete this text code:
preflight Run pre-flight checks
certs Certificate generation
/ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
/apiserver Generate the certificate for serving the Kubernetes API
/apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
/front-proxy-ca Generate the self-signed CA to provision identities for front proxy
/front-proxy-client Generate the certificate for the front proxy client
/etcd-ca Generate the self-signed CA to provision identities for etcd
/etcd-server Generate the certificate for serving etcd
/etcd-peer Generate the certificate for etcd nodes to communicate with each other
/etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
/apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
/sa Generate a private key for signing service account tokens along with its public key
kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
/admin Generate a kubeconfig file for the admin to use and for kubeadm itself
/super-admin Generate a kubeconfig file for the super-admin
/kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
/controller-manager Generate a kubeconfig file for the controller manager to use
/scheduler Generate a kubeconfig file for the scheduler to use
|
etcd Generate static Pod manifest file for local etcd
/local Generate the static Pod manifest file for a local, single-node local etcd instance
control-plane Generate all static Pod manifest files necessary to establish the control plane
/apiserver Generates the kube-apiserver static Pod manifest
/controller-manager Generates the kube-controller-manager static Pod manifest
/scheduler Generates the kube-scheduler static Pod manifest
kubelet-start Write kubelet settings and (re)start the kubelet
wait-control-plane Wait for the control plane to start
upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
/kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
/kubelet Upload the kubelet component config to a ConfigMap
upload-certs Upload certificates to kubeadm-certs
mark-control-plane Mark a node as a control-plane
bootstrap-token Generates bootstrap tokens used to join a node to a cluster
kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap
/enable-client-cert-rotation Enable kubelet client certificate rotation
addon Install required addons for passing conformance tests
/coredns Install the CoreDNS addon to a Kubernetes cluster
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster
show-join-command Show the join command for control-plane and worker node
|
text
|
code-example
|
kubeadm init | The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_completion_39
|
Explain this text code:
preflight Run pre-flight checks
certs Certificate generation
/ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
/apiserver Generate the certificate for serving the Kubernetes API
/apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
/front-proxy-ca Generate the self-signed CA to provision identities for front proxy
/front-proxy-client Generate the certificate for the front proxy client
/etcd-ca Generate the self-signed CA to provision identities for etcd
/etcd-server Generate the certificate for serving etcd
/etcd-peer Generate the certificate for etcd nodes to communicate with each other
/etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
/apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
/sa Generate a private key for signing service account tokens along with its public key
kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
/admin Generate a kubeconfig file for the admin to use and for kubeadm itself
/super-admin Generate a kubeconfig file for the super-admin
/kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
/controller-manager Generate a kubeconfig file for the controller manager to use
/scheduler Generate a kubeconfig file for the scheduler to use
etcd Generate static Pod manifest file for local etcd
/local Generate the static Pod manifest file for a local, single-node local etcd instance
control-plane Generate all static Pod manifest files necessary to establish the control plane
/apiserver Generates the kube-apiserver static Pod manifest
/controller-manager Generates the kube-controller-manager static Pod manifest
/scheduler Generates the kube-scheduler static Pod manifest
kubelet-start Write kubelet settings and (re)start the kubelet
wait-control-plane Wait for the control plane to start
upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
/kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
/kubelet Upload the kubelet component config to a ConfigMap
upload-certs Upload certificates to kubeadm-certs
mark-control-plane Mark a node as a control-plane
bootstrap-token Generates bootstrap tokens used to join a node to a cluster
kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap
/enable-client-cert-rotation Enable kubelet client certificate rotation
addon Install required addons for passing conformance tests
/coredns Install the CoreDNS addon to a Kubernetes cluster
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster
show-join-command Show the join command for control-plane and worker node
|
This text code kubeadm init | The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
text
|
code-example_explanation
|
kubeadm init | The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_40
|
Explain this shell code:
sudo kubeadm init phase control-plane controller-manager --help
|
This shell code kubeadm init | You can also use --help to see the list of sub-phases for a certain parent phase:
|
shell
|
code-example_explanation
|
kubeadm init | You can also use --help to see the list of sub-phases for a certain parent phase:
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_41
|
Complete this shell code:
sudo kubeadm init phase control-plane all --config=configfile.yaml
sudo kubeadm init phase etcd local --config=configfile.yaml
|
# you can now modify the control plane and etcd manifest files
sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
|
shell
|
code-example
|
kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_completion_42
|
Explain this shell code:
sudo kubeadm init phase control-plane all --config=configfile.yaml
sudo kubeadm init phase etcd local --config=configfile.yaml
# you can now modify the control plane and etcd manifest files
sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
|
This shell code kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
shell
|
code-example_explanation
|
kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_43
|
Explain this shell code:
kubeadm config images list
kubeadm config images pull
|
This shell code kubeadm init | You can pass --config to the above commands with a kubeadm configuration file to control the kubernetesVersion and imageRepository fields.
|
shell
|
code-example_explanation
|
kubeadm init | You can pass --config to the above commands with a kubeadm configuration file to control the kubernetesVersion and imageRepository fields.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_44
|
Explain this shell code:
kubeadm init phase upload-certs --upload-certs --config=SOME_YAML_FILE
|
This shell code kubeadm init | If a predefined certificate key is not passed to kubeadm init and kubeadm init phase upload-certs a new key will be generated automatically.
|
shell
|
code-example_explanation
|
kubeadm init | If a predefined certificate key is not passed to kubeadm init and kubeadm init phase upload-certs a new key will be generated automatically.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_45
|
Explain this text code:
sudo kubeadm init phase control-plane controller-manager --help
|
This text code kubeadm init | You can also use --help to see the list of sub-phases for a certain parent phase:
|
text
|
code-example_explanation
|
kubeadm init | You can also use --help to see the list of sub-phases for a certain parent phase:
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_46
|
Complete this text code:
sudo kubeadm init phase control-plane all --config=configfile.yaml
sudo kubeadm init phase etcd local --config=configfile.yaml
|
# you can now modify the control plane and etcd manifest files
sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
|
text
|
code-example
|
kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_completion_47
|
Explain this text code:
sudo kubeadm init phase control-plane all --config=configfile.yaml
sudo kubeadm init phase etcd local --config=configfile.yaml
# you can now modify the control plane and etcd manifest files
sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
|
This text code kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
text
|
code-example_explanation
|
kubeadm init | What this example would do is write the manifest files for the control plane and etcd in /etc/kubernetes/manifests based on the configuration in configfile.yaml. This allows you to modify the files an
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_48
|
Explain this text code:
kubeadm config images list
kubeadm config images pull
|
This text code kubeadm init | You can pass --config to the above commands with a kubeadm configuration file to control the kubernetesVersion and imageRepository fields.
|
text
|
code-example_explanation
|
kubeadm init | You can pass --config to the above commands with a kubeadm configuration file to control the kubernetesVersion and imageRepository fields.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_49
|
Explain this text code:
kubeadm init phase upload-certs --upload-certs --config=SOME_YAML_FILE
|
This text code kubeadm init | If a predefined certificate key is not passed to kubeadm init and kubeadm init phase upload-certs a new key will be generated automatically.
|
text
|
code-example_explanation
|
kubeadm init | If a predefined certificate key is not passed to kubeadm init and kubeadm init phase upload-certs a new key will be generated automatically.
|
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
|
k8s_00003_code_explain_50
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
apiServer:
|
extraArgs:
- name: "enable-admission-plugins"
value: "AlwaysPullImages,DefaultStorageClass"
- name: "audit-log-path"
value: "/home/johndoe/audit.log"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_51
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
apiServer:
extraArgs:
- name: "enable-admission-plugins"
value: "AlwaysPullImages,DefaultStorageClass"
- name: "audit-log-path"
value: "/home/johndoe/audit.log"
|
This yaml code Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_52
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
controllerManager:
|
extraArgs:
- name: "cluster-signing-key-file"
value: "/home/johndoe/keys/ca.key"
- name: "deployment-controller-sync-period"
value: "50"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_53
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
controllerManager:
extraArgs:
- name: "cluster-signing-key-file"
value: "/home/johndoe/keys/ca.key"
- name: "deployment-controller-sync-period"
value: "50"
|
This yaml code Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_54
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
scheduler:
extraArgs:
- name: "config"
|
value: "/etc/kubernetes/scheduler-config.yaml"
extraVolumes:
- name: schedulerconfig
hostPath: /home/johndoe/schedconfig.yaml
mountPath: /etc/kubernetes/scheduler-config.yaml
readOnly: true
pathType: "File"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_55
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
scheduler:
extraArgs:
- name: "config"
value: "/etc/kubernetes/scheduler-config.yaml"
extraVolumes:
- name: schedulerconfig
hostPath: /home/johndoe/schedconfig.yaml
mountPath: /etc/kubernetes/scheduler-config.yaml
readOnly: true
pathType: "File"
|
This yaml code Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_56
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
etcd:
|
local:
extraArgs:
- name: "election-timeout"
value: 1000
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_57
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
etcd:
local:
extraArgs:
- name: "election-timeout"
value: 1000
|
This yaml code Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_58
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: InitConfiguration
|
patches:
directory: /home/user/somedir
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_59
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: InitConfiguration
patches:
directory: /home/user/somedir
|
This yaml code Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_60
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: JoinConfiguration
|
patches:
directory: /home/user/somedir
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_61
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: JoinConfiguration
patches:
directory: /home/user/somedir
|
This yaml code Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_62
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
apiServer:
|
extraArgs:
- name: "enable-admission-plugins"
value: "AlwaysPullImages,DefaultStorageClass"
- name: "audit-log-path"
value: "/home/johndoe/audit.log"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_63
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
apiServer:
extraArgs:
- name: "enable-admission-plugins"
value: "AlwaysPullImages,DefaultStorageClass"
- name: "audit-log-path"
value: "/home/johndoe/audit.log"
|
This yaml code Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_64
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
controllerManager:
|
extraArgs:
- name: "cluster-signing-key-file"
value: "/home/johndoe/keys/ca.key"
- name: "deployment-controller-sync-period"
value: "50"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_65
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
controllerManager:
extraArgs:
- name: "cluster-signing-key-file"
value: "/home/johndoe/keys/ca.key"
- name: "deployment-controller-sync-period"
value: "50"
|
This yaml code Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_66
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
scheduler:
extraArgs:
- name: "config"
|
value: "/etc/kubernetes/scheduler-config.yaml"
extraVolumes:
- name: schedulerconfig
hostPath: /home/johndoe/schedconfig.yaml
mountPath: /etc/kubernetes/scheduler-config.yaml
readOnly: true
pathType: "File"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_67
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
scheduler:
extraArgs:
- name: "config"
value: "/etc/kubernetes/scheduler-config.yaml"
extraVolumes:
- name: schedulerconfig
hostPath: /home/johndoe/schedconfig.yaml
mountPath: /etc/kubernetes/scheduler-config.yaml
readOnly: true
pathType: "File"
|
This yaml code Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_68
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
etcd:
|
local:
extraArgs:
- name: "election-timeout"
value: 1000
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_69
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
etcd:
local:
extraArgs:
- name: "election-timeout"
value: 1000
|
This yaml code Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_70
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: InitConfiguration
|
patches:
directory: /home/user/somedir
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_71
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: InitConfiguration
patches:
directory: /home/user/somedir
|
This yaml code Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_72
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: JoinConfiguration
|
patches:
directory: /home/user/somedir
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_73
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: JoinConfiguration
patches:
directory: /home/user/somedir
|
This yaml code Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_74
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
apiServer:
|
extraArgs:
- name: "enable-admission-plugins"
value: "AlwaysPullImages,DefaultStorageClass"
- name: "audit-log-path"
value: "/home/johndoe/audit.log"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_75
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
apiServer:
extraArgs:
- name: "enable-admission-plugins"
value: "AlwaysPullImages,DefaultStorageClass"
- name: "audit-log-path"
value: "/home/johndoe/audit.log"
|
This yaml code Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-controller-manager.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_76
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
controllerManager:
|
extraArgs:
- name: "cluster-signing-key-file"
value: "/home/johndoe/keys/ca.key"
- name: "deployment-controller-sync-period"
value: "50"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_77
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
controllerManager:
extraArgs:
- name: "cluster-signing-key-file"
value: "/home/johndoe/keys/ca.key"
- name: "deployment-controller-sync-period"
value: "50"
|
This yaml code Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the reference documentation for kube-scheduler.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_78
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
scheduler:
extraArgs:
- name: "config"
|
value: "/etc/kubernetes/scheduler-config.yaml"
extraVolumes:
- name: schedulerconfig
hostPath: /home/johndoe/schedconfig.yaml
mountPath: /etc/kubernetes/scheduler-config.yaml
readOnly: true
pathType: "File"
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_79
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
kubernetesVersion: v1.16.0
scheduler:
extraArgs:
- name: "config"
value: "/etc/kubernetes/scheduler-config.yaml"
extraVolumes:
- name: schedulerconfig
hostPath: /home/johndoe/schedconfig.yaml
mountPath: /etc/kubernetes/scheduler-config.yaml
readOnly: true
pathType: "File"
|
This yaml code Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | For details, see the etcd server documentation.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_80
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
etcd:
|
local:
extraArgs:
- name: "election-timeout"
value: 1000
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_81
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: ClusterConfiguration
etcd:
local:
extraArgs:
- name: "election-timeout"
value: 1000
|
This yaml code Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | Kubeadm allows you to pass a directory with patch files to InitConfiguration and JoinConfiguration on individual nodes. These patches can be used as the last customization step before component config
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_82
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: InitConfiguration
|
patches:
directory: /home/user/somedir
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_83
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: InitConfiguration
patches:
directory: /home/user/somedir
|
This yaml code Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | You can pass this file to kubeadm join with --config <YOUR CONFIG YAML>:
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_84
|
Complete this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: JoinConfiguration
|
patches:
directory: /home/user/somedir
|
yaml
|
kubernetes-manifest
|
Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_completion_85
|
Explain this yaml code:
apiVersion: kubeadm.k8s.io/v1beta4
kind: JoinConfiguration
patches:
directory: /home/user/somedir
|
This yaml code Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
yaml
|
kubernetes-manifest_explanation
|
Customizing components with the kubeadm API | The directory must contain files named target[suffix][+patchtype].extension. For example, kube-apiserver0+merge.yaml or just etcd.json.
|
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/
|
k8s_00004_code_explain_86
|
Complete this text code:
# Print the supported API resources
kubectl api-resources
# Print the supported API resources with more information
kubectl api-resources -o wide
# Print the supported API resources sorted by a column
kubectl api-resources --sort-by=name
|
# Print the supported namespaced resources
kubectl api-resources --namespaced=true
# Print the supported non-namespaced resources
kubectl api-resources --namespaced=false
# Print the supported API resources with a specific APIGroup
kubectl api-resources --api-group=rbac.authorization.k8s.io
|
text
|
code-example
|
kubectl api-resources | Limit to resources in the specified API group.
|
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_api-resources/
|
k8s_00006_code_completion_87
|
Explain this text code:
# Print the supported API resources
kubectl api-resources
# Print the supported API resources with more information
kubectl api-resources -o wide
# Print the supported API resources sorted by a column
kubectl api-resources --sort-by=name
# Print the supported namespaced resources
kubectl api-resources --namespaced=true
# Print the supported non-namespaced resources
kubectl api-resources --namespaced=false
# Print the supported API resources with a specific APIGroup
kubectl api-resources --api-group=rbac.authorization.k8s.io
|
This text code kubectl api-resources | Limit to resources in the specified API group.
|
text
|
code-example_explanation
|
kubectl api-resources | Limit to resources in the specified API group.
|
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_api-resources/
|
k8s_00006_code_explain_88
|
Complete this text code:
# Print the supported API resources
kubectl api-resources
# Print the supported API resources with more information
kubectl api-resources -o wide
# Print the supported API resources sorted by a column
kubectl api-resources --sort-by=name
|
# Print the supported namespaced resources
kubectl api-resources --namespaced=true
# Print the supported non-namespaced resources
kubectl api-resources --namespaced=false
# Print the supported API resources with a specific APIGroup
kubectl api-resources --api-group=rbac.authorization.k8s.io
|
text
|
code-example
|
kubectl api-resources | Limit to resources in the specified API group.
|
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_api-resources/
|
k8s_00006_code_completion_89
|
Explain this text code:
# Print the supported API resources
kubectl api-resources
# Print the supported API resources with more information
kubectl api-resources -o wide
# Print the supported API resources sorted by a column
kubectl api-resources --sort-by=name
# Print the supported namespaced resources
kubectl api-resources --namespaced=true
# Print the supported non-namespaced resources
kubectl api-resources --namespaced=false
# Print the supported API resources with a specific APIGroup
kubectl api-resources --api-group=rbac.authorization.k8s.io
|
This text code kubectl api-resources | Limit to resources in the specified API group.
|
text
|
code-example_explanation
|
kubectl api-resources | Limit to resources in the specified API group.
|
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_api-resources/
|
k8s_00006_code_explain_90
|
Complete this yaml code:
apiVersion: apps/v1
kind: Deployment
metadata:
name: php-apache
spec:
selector:
matchLabels:
run: php-apache
template:
metadata:
labels:
run: php-apache
spec:
containers:
- name: php-apache
image: registry.k8s.io/hpa-example
ports:
|
- containerPort: 80
resources:
limits:
cpu: 500m
requests:
cpu: 200m
---
apiVersion: v1
kind: Service
metadata:
name: php-apache
labels:
run: php-apache
spec:
ports:
- port: 80
selector:
run: php-apache
|
yaml
|
deployment-definition
|
HorizontalPodAutoscaler Walkthrough | To do so, run the following command:
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_completion_91
|
Explain this yaml code:
apiVersion: apps/v1
kind: Deployment
metadata:
name: php-apache
spec:
selector:
matchLabels:
run: php-apache
template:
metadata:
labels:
run: php-apache
spec:
containers:
- name: php-apache
image: registry.k8s.io/hpa-example
ports:
- containerPort: 80
resources:
limits:
cpu: 500m
requests:
cpu: 200m
---
apiVersion: v1
kind: Service
metadata:
name: php-apache
labels:
run: php-apache
spec:
ports:
- port: 80
selector:
run: php-apache
|
This yaml code HorizontalPodAutoscaler Walkthrough | To do so, run the following command:
|
yaml
|
deployment-definition_explanation
|
HorizontalPodAutoscaler Walkthrough | To do so, run the following command:
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_92
|
Explain this bash code:
kubectl apply -f https://k8s.io/examples/application/php-apache.yaml
|
This bash code HorizontalPodAutoscaler Walkthrough | Now that the server is running, create the autoscaler using kubectl. The kubectl autoscale subcommand, part of kubectl, helps you do this.
|
bash
|
kubectl-command_explanation
|
HorizontalPodAutoscaler Walkthrough | Now that the server is running, create the autoscaler using kubectl. The kubectl autoscale subcommand, part of kubectl, helps you do this.
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_93
|
Explain this text code:
deployment.apps/php-apache created
service/php-apache created
|
This text code HorizontalPodAutoscaler Walkthrough | Now that the server is running, create the autoscaler using kubectl. The kubectl autoscale subcommand, part of kubectl, helps you do this.
|
text
|
code-example_explanation
|
HorizontalPodAutoscaler Walkthrough | Now that the server is running, create the autoscaler using kubectl. The kubectl autoscale subcommand, part of kubectl, helps you do this.
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_94
|
Explain this bash code:
kubectl autoscale deployment php-apache --cpu=50% --min=1 --max=10
|
This bash code HorizontalPodAutoscaler Walkthrough | You can check the current status of the newly-made HorizontalPodAutoscaler, by running:
|
bash
|
kubectl-command_explanation
|
HorizontalPodAutoscaler Walkthrough | You can check the current status of the newly-made HorizontalPodAutoscaler, by running:
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_95
|
Explain this text code:
horizontalpodautoscaler.autoscaling/php-apache autoscaled
|
This text code HorizontalPodAutoscaler Walkthrough | You can check the current status of the newly-made HorizontalPodAutoscaler, by running:
|
text
|
code-example_explanation
|
HorizontalPodAutoscaler Walkthrough | You can check the current status of the newly-made HorizontalPodAutoscaler, by running:
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_96
|
Explain this text code:
# You can use "hpa" or "horizontalpodautoscaler"; either name works OK.
kubectl get hpa
|
This text code HorizontalPodAutoscaler Walkthrough | The output is similar to:
|
text
|
code-example_explanation
|
HorizontalPodAutoscaler Walkthrough | The output is similar to:
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_97
|
Explain this text code:
NAME REFERENCE TARGET MINPODS MAXPODS REPLICAS AGE
php-apache Deployment/php-apache/scale 0% / 50% 1 10 1 18s
|
This text code HorizontalPodAutoscaler Walkthrough | (if you see other HorizontalPodAutoscalers with different names, that means they already existed, and isn't usually a problem).
|
text
|
code-example_explanation
|
HorizontalPodAutoscaler Walkthrough | (if you see other HorizontalPodAutoscalers with different names, that means they already existed, and isn't usually a problem).
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_98
|
Explain this text code:
# Run this in a separate terminal
# so that the load generation continues and you can carry on with the rest of the steps
kubectl run -i --tty load-generator --rm --image=busybox:1.28 --restart=Never -- /bin/sh -c "while sleep 0.01; do wget -q -O- http://php-apache; done"
|
This text code HorizontalPodAutoscaler Walkthrough | Now run:
|
text
|
code-example_explanation
|
HorizontalPodAutoscaler Walkthrough | Now run:
|
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
|
k8s_00007_code_explain_99
|
End of preview.
README.md exists but content is empty.
- Downloads last month
- 45