Kubernetes connector reaches end of life - 02-Nov-202

The Kubernetes connector for Insights, the agent (kubernetes-scanner) you deploy in your clusters to send workload configuration to Snyk, is reaching end of life.

What it did: the connector collected the list of images deployed in your clusters (with their IDs and SHAs) and the configuration of your services, such as networking. Snyk Insights used that information to understand what is deployed and which workloads are publicly accessible.

Snyk Insights has since been retired, and nothing in Snyk uses this data anymore.

On Nov 2nd 2026 , Snyk will stop accepting data from the connector. After that date, kubernetes-scanner will log errors when it tries to send data.

The Kubernetes integration (Snyk Controller, also called snyk-monitor) is a separate component and is not affected by this change.

The connector existed to feed Snyk Insights. Since Insights has been retired, the data the connector sends is no longer used, so we are retiring the service that receives it.

Customer's impact:

If you do not run the Kubernetes connector, nothing changes for you.

If you run the Kubernetes connector, After November 2nd, kubernetes-scanner will log errors because Snyk no longer accepts its data. We recommend uninstalling kubernetes-scanner from your clusters in advance to avoid those errors and to free the resources it uses. You can also remove the service account and custom role you created for it.

Read more about it: Kubernetes Connector Documentation