Set configuration context $kubectl config use-context k8s. Monitor the logs of Pod foobar and Extract
log lines corresponding to error unable-to-access-website . Write them to /opt/KULM00201/foobar
设置配置上下文$ kubectl config use-context k8s。监视Pod foobar的日志，并提取与error errors-to-access-website对应的日志行。将它们写入/ opt / KULM00201 / foobar
Set configuration context $kubectl config use-context k8s. List all PVs sorted by name, saving the full
kubectl output to /opt/KUCC0010/my_volumes. Use kubectl own functionally for sorting the output, and
do not manipulate it any further.
设置配置上下文$ kubectl config use-context k8s。列出所有按名称排序的PV，将完整的kubectl输出保存到/ opt / KUCC0010 / my_volumes。从功能上使用kubectl自己对输出进行排序，请勿对其进行任何进一步的操作。
If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string.
如果为非空，请使用此字段规范对列表类型进行排序。字段规范表示为JSONPath表达式（例如'{.metadata.name}'）。此JSONPath表达式指定的API资源中的字段必须为整数或字符串。
Set configuration context $kubectl config use-context k8s. Ensure a single instance of Pod nginx is
running on each node of the Kubernetes cluster where nginx also represents the image name which has
to be used. Do no override any taints currently in place. Use Daemonset to complete this task and use
ds.kusc00201 as Daemonset name.
设置配置上下文$ kubectl config use-context k8s。确保在Kubernetes集群的每个节点上都运行Pod nginx的单个实例，其中nginx还表示必须使用的映像名称。不要覆盖当前存在的任何污点。使用Daemonset完成此任务，并使用ds.kusc00201作为Daemonset名称。
Set configuration context $kubectl config use-context k8s Perform the following tasks: Add an init
container to lumpy-koala(which has been defined in spec file /opt/kucc00100/pod-spec-
KUCC00100.yaml). The init container should create an empty file named /workdir/calm.txt. If
/workdir/calm.txt is not detected, the Pod should exit. Once the spec file has been updated with the init
container definition, the Pod should be created.
设置配置上下文$ kubectl config use-context k8s执行以下任务：将初始化容器添加到lumpy-koala（已在规格文件/ opt / kucc00100 / pod-spec- KUCC00100.yaml中定义）。初始化容器应创建一个名为/workdir/calm.txt的空文件。如果未检测到/workdir/calm.txt，则Pod应该退出。一旦使用初始化容器定义更新了规范文件，就应该创建Pod。
Set configuration context $kubectl config use-context k8s. Create a pod named kucc4 with a single
container for each of the following images running inside(there may be between 1 and 4 images
specified):nginx +redis+Memcached+consul.
设置配置上下文$ kubectl config use-context k8s。创建一个名为kucc4的pod，该pod运行四个容器，每一个容器运行一种镜像（可能指定了1至4个镜像）：nginx + redis + Memcached + consul
Set configuration context $kubectl config use-context k8s Schedule a Pod as follows: Name: nginxkusc00101
Image: nginx Node selector: disk=ssd
设置配置上下文$ kubectl config use-context k8s调度Pod，如下所示：名称：nginxkusc00101 镜像：nginx 节点选择器：disk = ssd
Set configuration context $kubectl config use-context k8s. Create a deployment as follows: Name: nginxapp
Using container nginx with version 1.11.9-alpine. The deployment should contain 3 replicas. Next,
deploy the app with new version 1.12.0-alpine by performing a rolling update and record that update.
Finally,rollback that update to the previous version 1.11.9-alpine.
设置配置上下文$ kubectl config use-context k8s。创建如下的部署：名称：nginxapp将容器nginx与1.11.9-alpine版本一起使用。部署应包含3个副本。接下来，通过执行滚动更新并记录该更新，以新版本1.12.0-alpine部署该应用程序。最后，将更新回滚到先前的1.11.9-alpine版本
Set configuration context $kubectl config use-context k8s Create and configure the service front-endservice
so it’s accessible through NodePort/ClusterIp and routes to the existing pod named front-end
设置配置上下文$ kubectl config use-context k8s创建并配置服务前端服务，以便可以通过NodePort / ClusterIp访问该服务，并将其路由到名为front-end的pod
Set configuration context $kubectl config use-context k8s Create a Pod as follows: Name: jenkins Using
image: jenkins In a new Kubernetes namespace named website-frontend
设置配置上下文$ kubectl config use-context k8s创建Pod，如下所示：名称：jenkins 使用镜像：jenkins在名为website-frontend的新Kubernetes命名空间中
Set configuration context $kubectl config use-context k8s Create a deployment spec file that will: Launch
7 replicas of the redis image with the label : app_enb_stage=dev Deployment name: kual00201 Save a
copy of this spec file to /opt/KUAL00201/deploy_spec.yaml (or .json) When you are done,clean up(delete)
any new k8s API objects that you produced during this task
设置配置上下文$ kubectl config use-context k8s创建一个部署规范文件，该文件将：启动带有标签：app_enb_stage = dev的redis映像的7个副本 部署名称：kual00201 将此规范文件的副本保存到/ opt /KUAL00201/deploy_spec.yaml（或.json）完成后，清理（删除）在此任务期间生成的所有新k8s API对象
Set configuration context $kubectl config use-context k8s Create a file /opt/KUCC00302/kucc00302.txt
that lists all pods that implement Service foo in Namespace production. The format of the file should be
one pod name per line.
设置配置上下文$ kubectl config use-context k8s创建一个文件/opt/KUCC00302/kucc00302.txt，其中列出了在命名空间生产中实现Service foo的所有Pod。文件格式应为每行一个pod名称。
Set configuration context $kubectl config use-context k8s Create a Kubernetes Secret as follows: Name:
super-secret Credential: alice or username: bob Create a Pod named pod-secrets-via-file using the redis
image which mounts a secret named super-secret at /secrets. Create a second Pod named pod-secretsvia-
env using the redis image, which exports credential/username as TOPSECRET/CREDENTIALS.
设置配置上下文$ kubectl config use-context k8s创建Kubernetes Secret，如下所示：名称：super-secret凭据：alice或username：bob使用redis镜像创建一个名为pod-secrets-via-file的Pod，该文件会挂载一个名为super-secret的secret在/ secrets。使用redis镜像创建另一个名为pod-secrets-via-env的Pod，该pod将凭据/用户名导出为TOPSECRET/CREDENTIALS。
Set configuration context $kubectl config use-context k8s Create a pod as follows: Name: nonpersistent-
redis Container image: redis Named-volume with name: cache-control Mount path :
/data/redis It should launch in the pre-prod namespace and the volume MUST NOT be persistent.
设置配置上下文$ kubectl config use-context k8s如下创建一个pod：名称：nonpersistent- redis 容器镜像：redis名称为-volume的名称为：cache-control挂载路径：/data/redis它应在pre-prod名称空间中启动并且该卷一定不能持久。
Set configuration context $kubectl config use-context k8s Scale the deployment webserver to 6 pods
设置配置上下文$ kubectl config use-context k8s将部署Web服务器扩展到6个pod
Set configuration context $kubectl config use-context k8s Check to see how many nodes are ready (not
including nodes tainted NoSchedule) and write the number to /opt/nodenum.
设置配置上下文$ kubectl config use-context k8s检查以查看准备就绪的节点数（不包括受NoSchedule污染的节点），并将数目写入/opt/nodenum
Set configuration context $kubectl config use-context k8s From the Pod label name=cpu-utilizer, find
pods running high CPU workloads and write the name of the Pod consuming most CPU to the file
/opt/cpu.txt (which already exists).
设置配置上下文$ kubectl config use-context k8s从Pod标签名称= cpu-utilizer中，找到运行CPU高工作负载的Pod，并将消耗最多CPU的Pod名称写到文件/opt/cpu.txt（已存在）中
Set configuration context $kubectl config use-context k8s From the Pod label name=cpu-utilizer, find
pods running high CPU workloads and write the name of the Pod consuming most CPU to the file
/opt/cpu.txt (which already exists).
设置配置上下文$ kubectl config use-context k8s从Pod标签名称= cpu-utilizer中，找到运行CPU高工作负载的Pod，并将消耗最多CPU的Pod名称写到文件/opt/cpu.txt（已存在）中
Set configuration context $kubectl config use-context k8s Create a deployment as follows: Name: nginxdns
Exposed via a service : nginx-dns Ensure that the service & pod are accessible via their respective
DNS records The container(s) within any Pod(s) running as a part of this deployment should use the
nginx image. Next, use the utility nslookup to look up the DNS records of the service & pod and write the
output to /opt/service.dns and /opt/pod.dns respectively. Ensure you use the busybox:1.28 image (or
earlier) for any testing, an the latest release has an upstream bug which impacts the use of nslookup.
设置配置上下文$ kubectl config use-context k8s创建部署，如下所示：名称：nginxdns 通过service公开：nginx-dns确保通过各自的DNS记录可访问服务。和Pod任何Pod中的容器）作为此部署的一部分运行，则应使用nginx映像。接下来，使用实用程序nslookup查找服务和pod的DNS记录，并将输出分别写入/opt/service.dns和/opt/pod.dns。确保您使用busybox：1.28映像（或更早版本）进行任何测试，最新版本的上游错误会影响nslookup的使用。
No configuration context change required for this item Create a snapshot of the etcd instance running
at https://127.0.0.1:2379 saving the snapshot to the file path /data/backup/etcd-snapshot.db The etcd
instance is running etcd version 3.2.18 The following TLS certificates/key are supplied for connecting to
the server with etcdctl CA certificate: /opt/KUCM00302/ca.crt Client certificate: /opt/KUCM00302/etcdclient.
crt Client key: /opt/KUCM00302/etcd-client.key
此项无需配置上下文更改。创建在https://127.0.0.1:2379运行的etcd实例的快照，将快照保存到文件路径/data/backup/etcd-snapshot.db。etcd实例正在运行etcd版本3.2.18提供了以下TLS证书/密钥，用于使用etcdctl CA证书连接到服务器：/opt/KUCM00302/ca.crt客户端证书：/ opt / KUCM00302 / etcdclient。 crt客户端密钥：/opt/KUCM00302/etcd-client.key
Set configuration context $kubectl configuse-context bk8s Given a partially-functioning Kubernetes
cluser, identify symptoms of failure on the cluter. Determine the node, the failing service and take
actions to bring up the failed service and restore the health of the cluser. Ensure that any changes are
made permanently. The worker node in this cluster is labelled with name=bk8s-node-0 Hints: You can
ssh to the relevant nodes using $ssh $(NODE) where $(NODE) is one of bk8s-master-0 or bk8s-node-0.
You can assume elevated privileges on any node in the cluster with the following command: $ sudo -i.
设置配置上下文$ kubectl configuse-context bk8s给定部分运行的Kubernetes cluser，请确定该群集故障的症状。确定节点，发生故障的服务，并采取措施启动发生故障的服务并恢复cluser的运行状况。确保所有更改都是永久性的。该集群中的工作节点标记为name = bk8s-node-0提示：您可以使用$ ssh $（NODE）SSH到相关节点，其中$（NODE）是bk8s-master-0或bk8s-node- 0。您可以使用以下命令在群集中的任何节点上假定特权提升：$ sudo -i。