Table of Contents

1. Challenge

   Enable the LimitRanger Admission Controller

   • Use a text editor to modify the kube-apiserver.yaml and ensure that the LimitRanger admission controller is enabled.
   • Validate that the kube-apiserver pod redeploys successfully by issuing a simple kubectl command (the pod can take several seconds to redeploy).
2. Challenge

   Create a LimitRange Resource in the dev Namespace

   • Create a manifest file called mem-limit.yaml with the following specifications:

     Note: performing a copy paste directly from the objective will result in additional spaces being added. To remove additional spaces, either copy to a text editor on your computer before copying to the file on the host or manually remove the spaces once you have copied the file.

   apiVersion: v1
   kind: LimitRange
   metadata:
     name: mem-limit-range
     namespace: dev
   spec:
     limits:
     - default:
         memory: 512Mi
       defaultRequest:
         memory: 256Mi
       type: Container
   

   • Use the kubectl command to deploy the manifest file.
3. Challenge

   Create Two Pods in the dev Namespace

   • View the contents of the nginx-pod.yaml file in the /home/cloud_user directory (take note of any memory requests or limits, if they appear):
     • Use the kubectl command to deploy the manifest.
     • Use the kubectl command to print information about the pod in YAML format (pay attention to the memory request and limit).
   • View the contents of the test-pod.yaml file in the /home/cloud_user directory (take note of any memory requests or limits, if they appear):
     • Use the kubectl command to deploy the manifest.
     • Use the kubectl command to print information about the pod in YAML format (pay attention to the memory request and limit).