Hao DevSecOps

Task weight: 2% Use context: kubectl config use-context k8s-c2-AC Node cluster2-node1 has been added to the cluster using kubeadm and TLS bootstrapping. Find the “Issuer” and “Extended Key Usage” values of the cluster2-node1: kubelet client certificate, the one used for outgoing connections to the kube-apiserver. kubelet server certificate, the one used for incoming connections from the kube-apiserver. Write the information into file /opt/course/23/certificate-info.txt . Compare the “Issuer” ...

Task weight: 2% Use context: kubectl config use-context k8s-c2-AC Check how long the kube-apiserver server certificate is valid on cluster2-controlplane1 . Do this with openssl or cfssl. Write the exipiration date into /opt/course/22/expiration . Also run the correct kubeadm command to list the expiration dates and confirm both methods show the same date. Write the correct kubeadm command that would renew the apiserver server certificate into /opt/course/22/kubeadm-renew-certs.sh . 译文在 clust...

Use context: kubectl config use-context k8s-c3-CCC Create a Static Pod named my-static-pod in Namespace default on cluster3-controlplane1 . It should be of image nginx:1.16-alpine and have resource requests for 10m CPU and 20Mi memory. Then create a NodePort Service named static-pod-service which exposes that static Pod on port 80 and check if it has Endpoints and if it’s reachable through the cluster3-controlplane1 internal IP address. You can connect to the internal node IPs from your main ...

Use context: kubectl config use-context k8s-c3-CCC Your coworker said node cluster3-node2 is running an older Kubernetes version and is not even part of the cluster. Update Kubernetes on that node to the exact version that’s running on cluster3-controlplane1 . Then add this node to the cluster. Use kubeadm for this. 译文你的同事说 cluster3-node2 节点运行的是旧的Kubernetes版本，甚至不是集群的一部分。将该节点上的Kubernetes版本更新为 cluster3-controlplane1 上运行的版本。使用kubeadm把这个节点添加到集群中。2023-01-10 15:33 kubectl config use-context k8s-c3...

Task weight: 3% NOTE: This task can only be solved if questions 18 or 20 have been successfully implemented and the k8s-c3-CCC cluster has a functioning worker node Use context: kubectl config use-context k8s-c3-CCC Do the following in a new Namespace secret . Create a Pod named secret-pod of image busybox:1.31.1 which should keep running for some time. There is an existing Secret located at /opt/course/19/secret1.yaml , create it in the Namespace secret and mount it readonly into the Pod a...

Use context: kubectl config use-context k8s-c3-CCC There seems to be an issue with the kubelet not running on cluster3-node1 . Fix it and confirm that cluster has node cluster3-node1 available in Ready state afterwards. You should be able to schedule a Pod on cluster3-node1 afterwards. Write the reason of the issue into /opt/course/18/reason.txt . 译文在 cluster3-node1 上运行的 kubelet 似乎有问题。 修复该问题并确认集群中的 cluster3-node1 节点处于就绪状态。 之后，您应该可以在 cluster3-node1 上调度 Pod。 将问题原因写入 /opt/course/18/reason.txt 。...

Use context: kubectl config use-context k8s-c1-H In Namespace project-tiger create a Pod named tigers-reunite of image httpd:2.4.41-alpine with labels pod=container and container=pod . Find out on which node the Pod is scheduled. Ssh into that node and find the containerd container belonging to that Pod. Using command crictl : Write the ID of the container and the info.runtimeType into /opt/course/17/pod-container.txt Write the logs of the container into /opt/course/17/pod-container.log 译文在...

Use context: kubectl config use-context k8s-c1-H Write the names of all namespaced Kubernetes resources (like Pod, Secret, ConfigMap…) into /opt/course/16/resources.txt . Find the project-* Namespace with the highest number of Roles defined in it and write its name and amount of Roles into /opt/course/16/crowded-namespace.txt . 译文将所有命名的 Kubernetes 资源（如 Pod、Secret、ConfigMap……）的名称写入 /opt/course/16/resources.txt 中。 查找定义角色数量最多的 *project-*** 命名空间，并将其名称和角色数量写入 /opt/course/16/crowded-namespace.txt ...

Use context: kubectl config use-context k8s-c2-AC Write a command into /opt/course/15/cluster_events.sh which shows the latest events in the whole cluster, ordered by time ( metadata.creationTimestamp ). Use kubectl for it. Now kill the kube-proxy Pod running on node cluster2-node1 and write the events this caused into /opt/course/15/pod_kill.log . Finally kill the containerd container of the kube-proxy Pod on node cluster2-node1 and write the events into /opt/course/15/container_kill.log . ...

Use context: kubectl config use-context k8s-c1-H You’re ask to find out following information about the cluster k8s-c1-H : How many controlplane nodes are available? How many worker nodes are available? What is the Service CIDR? Which Networking (or CNI Plugin) is configured and where is its config file? Which suffix will static pods have that run on cluster1-node1? Write your answers into file /opt/course/14/cluster-info , structured like this: # /opt/course/14/cluster-info1: [ANSWER]2: [AN...