The DevOps team would like to get the list of all Namespaces in the cluster. Get the list
and save it to /opt/course/1/namespaces. - answerk get ns > /opt/course/1/namespaces
Create a single Pod of image httpd:2.4.41-alpine in Namespace default. The Pod should
be named pod1 and the container should be named pod1-container. - answerk run #
help
# check the export on the very top of this document so we can use $do
k run pod1 --image=httpd:2.4.41-alpine $do > 2.yaml
vim 2.yaml
Change the container name in 2.yaml to pod1-container:
Your manager would like to run a command manually on occasion to output the status
of that exact pod1. Please write a command that does this into /opt/course/2/pod1-
status-command.sh. The command should use kubectl. - answerNext create the
requested command:
vim /opt/course/2/pod1-status-command.sh
The content of the command file could look like:
# /opt/course/2/pod1-status-command.sh
kubectl -n default describe pod pod1 | grep -i status:
To test the command:
➜ sh /opt/course/2/pod1-status-command.sh
Running
Team Neptune needs a Job template located at /opt/course/3/job.yaml. This Job should
run image busybox:1.31.0 and execute
sleep 2 && echo done.
It should be in namespace neptune, run a total of 3 times and should execute 2 runs in
parallel. - answerk -n neptun create job -h
, # check the export on the very top of this document so we can use $do
k -n neptune create job neb-new-job --image=busybox:1.31.0 $do >
/opt/course/3/job.yaml -- sh -c "sleep 2 && echo done"
vim /opt/course/3/job.yaml
make the required changes in the yaml:
Then to create it:
k -f /opt/course/3/job.yaml create
# namespace already set in yaml
Start the Job and check its history. Each pod created by the Job should have the label
id: awesome-job. The job should be named neb-new-job and the container neb-new-
job-container. - answerCheck Job and Pods, you should see two running parallel at
most but three in total:
k -n neptune get pod,job | grep neb-new-job
Check job history:
k -n neptune describe job neb-new-job
Team Mercury asked you to perform some operations using Helm, all in Namespace
mercury:
Delete release internal-issue-report-apiv1 - answerFirst we should delete the required
release:
helm -n mercury ls
➜ helm -n mercury ls
NAME NAMESPACE STATUS CHART APP VERSION
internal-issue-report-apiv1 mercury deployed nginx-9.5.0 1.21.1
internal-issue-report-apiv2 mercury deployed nginx-9.5.0 1.21.1
internal-issue-report-app mercury deployed nginx-9.5.0 1.21.1
➜ helm -n mercury ls
NAME NAMESPACE STATUS CHART APP VERSION
internal-issue-report-apiv2 mercury deployed nginx-9.5.0 1.21.1
internal-issue-report-app mercury deployed nginx-9.5.0 1.21.1
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller Dreamer252. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $13.49. You're not tied to anything after your purchase.