Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon
Labs

Automate Kubernetes Image Vulnerability Scanning

Container image vulnerabilities can be a major attack vector for your Kubernetes infrastructure. In this lab, you will implement automated image scanning to ensure that severely vulnerable images do not run in your cluster.

Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Advanced
Duration
Clock icon 30m
Published
Clock icon Jun 04, 2021

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Configure the Admission Controller

    You will find a skeleton admission control configuration at /etc/kubernetes/admission-control/admission-control.conf. Configure the admission controller by adding the necessary configuration to this file.

    When configuring the admission controller:

    • The kubeconfig is located at /etc/kubernetes/admission-control/imagepolicy_backend.kubeconfig.
    • Configure the admission controller to deny workload creation by default, even if the backend webhook cannot be reached.
  2. Challenge

    Edit the Admission Controller's kubeconfig to Point to the Backend Webhook

    Modify the admission controller's kubeconfig to point to the backend service.

    The kubeconfig is located at /etc/kubernetes/admission-control/imagepolicy_backend.kubeconfig.

    The backend service can be reached at acg.trivy.k8s.webhook:8090/scan.

    Certificates are already set up in the kubeconfig, and the API server is already set up to be able to locate these certificate files.

  3. Challenge

    Enable Any Necessary Admission Control Plugins

    Configure the API server to enable any necessary admission control plugins.

    Once this is done, the API server should be using the backend webhook to scan images and deny workloads that have major vulnerabilities.

    You can find Pod manifest files in /home/cloud_user you can use to test your setup. The Pod defined in good-pod.yml should succeed, while the Pod in bad-pod.yml should fail to be created due to image vulnerabilities.

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans