Product updates
Sign up for free

Submit a Support ticket Sign in to Support Sign up for free

 

Scan your Kubernetes configuration files

  1. Docs Library | Snyk
  2. Infrastructure as code
  3. Scan your Kubernetes configuration files

Scan and fix security issues in your Helm Charts

Snyk scans Helm Charts, in addition to Kubernetes configuration files, for misconfigurations and security issues. Once Helm Charts are scanned, Snyk creates projects for each template and dependency template, generates reports on any misconfigurations, and makes recommendations for fixing them.

Prerequisites

  • An administrator should connect your organization with your preferred Git repository and enable detection of configuration files as described here.

  • The repository should follow the standard Chart directory structure. Specifically we look for:
    • Chart.yaml - YAML file containing information about the chart
    • values.yaml - The default configuration values for this chart
    • templates/ - A directory of templates that, when combined with values will generate valid Kubernetes manifest files.
    • Values - An optional directory of values that used to configure different environments.
    • requirements.yaml - Optional file - Additional way to declare dependencies

Scan and fix your Charts

  1. Log in to your account and navigate to the relevant group and organization that you want to manage.

    AddProjectMenu.gif

  2. If you already imported your repositories for testing before cloud configuration file detection was enabled by your administrator, then you should re-import that repository again in order to import the Helm chart:
    2.1.png

     


    2.2.png

  3. Every time a repository is scanned:

    • Each template in your Helm Chart creates a Snyk a project, grouped together by repository, similar to this example:

      Screenshot_2020-04-24_at_08.50.36.png

    • If you re-imported the repository in order to import the cloud configuration files, then Snyk imports and tests the configuration files and also re-tests the already imported application manifest files - displaying the test time as "now".

  4. Click the project link you're interested in, to view the scan results and to correct your configuration files accordingly:

    • Projects that were created from external dependencies will also be scanned and issues shown.

      Screenshot_2020-04-24_at_08.51.18.png
     

    Note

    For more information about these results, see Working with your Kubernetes configuration file test results.