Challenge, Easy,  on  Kubernetes

Enforce Resource Policies Using LimitRange

Scenario

A namespace project-x already exists in the cluster. The platform team wants to enforce resource policies for all containers running in this namespace.

Task

  1. Create a LimitRange named projectx-limits in the project-x namespace that applies to containers only with the following rules:
    • Minimum CPU request: 100m, Minimum Memory request: 128Mi
    • Maximum CPU limit: 800m, Maximum Memory limit: 1Gi
    • If developers do not specify resources, the following defaults will be applied automatically:
      ResourceDefault RequestDefault Limit
      CPU200m500m
      Memory256Mi512Mi
  2. Ensure the LimitRange applies to containers only.
  3. Create a Pod named ml-worker using the image nginx in the same namespace.
  4. Ensure the Pod's resource configuration does not exceed the default request and default limit values defined in the LimitRange.
  5. Verify that the Pod is successfully created and complies with the LimitRange policies.
Hint 1

A LimitRange uses min, max, default, and defaultRequest fields under spec.limits. Set type: Container to apply rules to containers only. See the official docs: LimitRange

Test Cases

How to Author Challenges on iximiuz Labs

Instead of providing a subpar online editing experience, iximiuz Labs offers a helper CLI tool called labctl, allowing you to use your favorite text editor (or a full-featured IDE) to write content from the comfort of your local machine.

Install labctl CLI

curl -sf https://labs.iximiuz.com/cli/install.sh | sh

This will download and install the latest version of the labctl CLI. You only need to do this once per workstation.

Authorize labctl

labctl auth login

This will open a browser window asking you to authorize labctl to access your account. You need to do it after a fresh install of labctl and repeat it whenever the auth session expires.

Pull challenge content

labctl content pull challenge enforce-resource-policies-using-limitRange-e8455673

This will create a local copy of the challenge content in a directory named enforce-resource-policies-using-limitRange-e8455673. You only need to do this once per challenge.

Stream your changes

labctl content push -fw challenge enforce-resource-policies-using-limitRange-e8455673

Run this command in a separate terminal to continuously upload your changes to the server while editing the challenge in your favorite text editor or IDE.

You can also use labctl to create, list, and delete your content. Learn more about the available commands: labctl content --help

Start challenge