It is important to note that 1 Snyk organization has a limit of 25,000 projects, please consult your SCM for more information.
You must have an account with Snyk and be onboarded to your organization by an administrator.
In addition the integration must be configured between Snyk and your Kubernetes environment per organization. To verify the integration is configured, ensure you have an Integration ID****
You can configure the Snyk controller to automatically import and update scanned workloads directly in Snyk to test and monitor for vulnerabilities. You can also automatically delete imported projects once workloads are deleted from the cluster.
Enabling workload auto-import and auto-delete
The Helm chart of the Snyk controller is already provisioned with a default policy to process events for any workload except Jobs and Pods. To enable this feature, provide your Snyk Organization public ID in the Helm chart installation.
Note that policyOrgs is a list of organization public IDs. You can add more than one organization to use the auto-import and auto-delete capabilities. You can locate this public ID under your organization's settings page.
Only Snyk organizations that share the same Kubernetes integration ID can provision the Snyk controller to do so. More information on how to share the same integration ID can be found in Clone an integration across your Snyk orgs.
Once an administrator for your Snyk account has installed the Snyk controller on your Kubernetes cluster, add workloads for testing. Kubernetes collaborators can mark workloads from the cluster to be automatically added to Snyk
Automatically add, update and remove workloads
Once you’ve configured the integration between Snyk and your cluster, you can annotate your workloads in order to have them automatically added as projects for testing in Snyk.
The annotated import happens when the image itself changes (rescans the workload due to image change) or when the workload details change (which creates a new revision of the workload). Changing the annotation for the workload will not cause a workload change.
If the workload is only annotated after it has been scanned by snyk monitor the annotation will not be recognized until a significant change takes place that causes a full rescan. Terminating the snyk monitor pod is one way to force a rescan.
Annotate any of the following workload types:
The steps follow:
Log in to your account and navigate to the relevant group and organization that you want to manage.
Click on settings
Copy the Organization ID value.
Add an annotation to the workload with the key orgs.k8s.snyk.io/v1, entering the Organization ID as the value in a comma-separated list.
You can also annotate a single workload to be added to multiple organizations.
The Snyk controller automatically picks up on the changes to your workload and ensures that the workload is automatically imported to Snyk as a Snyk project.
Example: Deployment YAML file annotated to be automatically imported into an organization
To annotate for multiple organizations use a comma-separated list.
Once imported, the project remains in your Snyk organization even if you remove the annotation. To remove the project from Snyk, you should delete the annotation and delete it from the Snyk UI or with the API.