Helm Chart 0.19.0 (controller version 0.17.0) - Deprecated CRDs

[jonstacks]

What

Starting in Helm chart version 0.19.0 (controller version 0.17.0) we will be deprecating the following CRDs:

• HTTPSEdge
• TLSEdge
• TCPEdge
• Tunnel
• NgrokModuleSet

They will be removed in a future version of the ngrok-operator. It is suggested that you migrate off of these resources as soon as possible to avoid disruptions in future versions.

Why

The corresponding API resources will be sunset and turned off in ngrok on December 31st, 2025. As such, we will not be able to reconcile these resources in the ngrok API.

How

Helm chart version 0.18.0 (controller version 0.16.0) switched to using endpoints as the default mapping strategy instead of edges. Unless you are manually creating HTTPSEdge, TLSEdge, TCPEdge, Tunnel, or NgrokModuleSet CRs, you should have been automatically migrated to using Cloud & Agent Endpoints.

NgrokModuleSets are the exception as they were created by users and placed in annotations on Ingress and Load Balancer Services. Once you are no longer referencing these via annotations, you can delete your NgrokModuleSet CRs.

You can check if you are currently using any of these resources with:

kubectl get httpsedges.ingress.k8s.ngrok.com -A
kubectl get tlsedges.ingress.k8s.ngrok.com -A
kubectl get tcpedges.ingress.k8s.ngrok.com -A
kubectl get tunnels.ingress.k8s.ngrok.com -A
kubectl get ngrokmodulesets.ingress.k8s.ngrok.com -A

Resources:

• https://ngrok.com/docs/universal-gateway/edges/#migration-guide
• https://ngrok.com/blog-post/introducing-cloud-endpoints