--- title: ngrok-operator v0.19.0: Gateway API updates and edge... description: Version 0.19.0 of the ngrok-operator helm chart adds Gateway API improvements including .Status.Addresses population for ExternalDNS integration and status... canonical: https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: ngrok-operator v0.19.0: Gateway API updates and edge deprecation | daily.dev og:description: Version 0.19.0 of the ngrok-operator helm chart adds Gateway API improvements including .Status.Addresses population for ExternalDNS integration and status... og:url: https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla og:image: https://api.daily.dev/og/posts/hqCQEgQla.png og:image:alt: ngrok-operator v0.19.0: Gateway API updates and edge deprecation og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # ngrok-operator v0.19.0: Gateway API updates and edge deprecation **[ngrok Blog](https://daily.dev/sources/ngrok)** · 3 min read · 0 upvotes · 0 comments ## Summary Version 0.19.0 of the ngrok-operator helm chart adds Gateway API improvements including .Status.Addresses population for ExternalDNS integration and status conditions matching community standards (now consumed by Argo CD v3.1.0). It also introduces per-domain deletion policies via a defaultDomainReclaimPolicy helm value. Most notably, it deprecates the Tunnel, HTTPSEdge, TLSEdge, TCPEdge, and NgrokModuleSet CRDs ahead of the Edges feature set being fully removed from ngrok by the end of the year, in favor of the newer Endpoints model (CloudEndpoint, AgentEndpoint, and TrafficPolicy resources). ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is ngrok-operator deprecating the HTTPSEdge, TLSEdge, TCPEdge, and Tunnel CRDs? They are deprecated in ngrok-operator 0.19.0 because ngrok is removing the Edges feature set entirely by the end of the year in favor of Endpoints. HTTPSEdge, TLSEdge, and TCPEdge are unified under the new CloudEndpoint CRD, Tunnel is replaced by AgentEndpoint, and NgrokModuleSet is replaced by TrafficPolicy. Removal follows in the next ngrok-operator release. _Track deprecation timelines like this on daily.dev before an ngrok-operator upgrade breaks your ingress setup._ ### How do I stop ngrok-operator from deleting a Domain resource in ngrok when I delete the Kubernetes CR? Set the defaultDomainReclaimPolicy helm value to Retain when installing or upgrading the ngrok-operator chart to version 0.19.0 or later. Previously, deleting the Ingress, Gateway, or LB service's Domain CR always deleted the corresponding domain in ngrok; domains created before this version keep the default Delete behavior unless explicitly changed. _Developers configuring ingress domain lifecycles follow ngrok-operator changes like this on daily.dev._ ### How does Argo CD show the health of ngrok Gateway API resources? Starting with Argo CD v3.1.0, it reads and displays the Gateway API status conditions that ngrok-operator 0.19.0 now sets on gateways and listeners, such as a Programmed condition indicating whether the configuration was accepted and applied in ngrok's cloud. This makes debugging Gateway API configurations visible directly in the Argo CD UI. _Platform engineers wiring GitOps tools to Gateway API status can find integration updates like this on daily.dev._ ## Similar posts on daily.dev - [Ingress NGINX is EOL: A practical guide for migrating to Kubernetes Gateway API](https://daily.dev/posts/ingress-nginx-is-eol-a-practical-guide-for-migrating-to-kubernetes-gateway-api-fj854bzvi) · Datadog · 0 upvotes · 0 comments - [CNCF Retires the Ingress Nginx Controller for Kubernetes](https://daily.dev/posts/cncf-retires-the-ingress-nginx-controller-for-kubernetes-ldynums2g) · The New Stack · 3 upvotes · 0 comments - [Understanding the Ingress-NGINX Deprecation — Before You Migrate to the Gateway API](https://daily.dev/posts/understanding-the-ingress-nginx-deprecation-before-you-migrate-to-the-gateway-api-eibylkte5) · ITNEXT · 6 upvotes · 0 comments - [How to Move to the Gateway API: post ingress-nginx Retirement](https://daily.dev/posts/how-to-move-to-the-gateway-api-post-ingress-nginx-retirement-q3cqencll) · Pulumi · 5 upvotes · 0 comments --- Tags: [#devtools](https://daily.dev/tags/devtools), [#kubernetes](https://daily.dev/tags/kubernetes), [#gateway-api](https://daily.dev/tags/gateway-api) [View this post on daily.dev](https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"ngrok-operator v0.19.0: Gateway API updates and edge deprecation","url":"https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla"},"datePublished":"2026-08-23T07:21:03.123Z","dateModified":"2026-08-23T07:26:57.510Z","description":"Version 0.19.0 of the ngrok-operator helm chart adds Gateway API improvements including .Status.Addresses population for ExternalDNS integration and status...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/53a610e1d64b439fda3ebb9aaf7eeb4e?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/53a610e1d64b439fda3ebb9aaf7eeb4e?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ngrok Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ngrok Blog","logo":"https://media.daily.dev/image/upload/s--718XXxvE--/f_auto,q_auto/v1787469610/logos/ngrok?_a=BAMAMicg0","url":"https://daily.dev/sources/ngrok"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devtools,kubernetes,gateway-api","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ngrok Blog","item":"https://daily.dev/sources/ngrok"},{"@type":"ListItem","position":3,"name":"ngrok-operator v0.19.0: Gateway API updates and edge deprecation"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/ngrok-operator-v0-19-0-gateway-api-updates-and-edge-deprecation-hqcqegqla#faq","mainEntity":[{"@type":"Question","name":"Why is ngrok-operator deprecating the HTTPSEdge, TLSEdge, TCPEdge, and Tunnel CRDs?","acceptedAnswer":{"@type":"Answer","text":"They are deprecated in ngrok-operator 0.19.0 because ngrok is removing the Edges feature set entirely by the end of the year in favor of Endpoints. HTTPSEdge, TLSEdge, and TCPEdge are unified under the new CloudEndpoint CRD, Tunnel is replaced by AgentEndpoint, and NgrokModuleSet is replaced by TrafficPolicy. Removal follows in the next ngrok-operator release. Track deprecation timelines like this on daily.dev before an ngrok-operator upgrade breaks your ingress setup."}},{"@type":"Question","name":"How do I stop ngrok-operator from deleting a Domain resource in ngrok when I delete the Kubernetes CR?","acceptedAnswer":{"@type":"Answer","text":"Set the defaultDomainReclaimPolicy helm value to Retain when installing or upgrading the ngrok-operator chart to version 0.19.0 or later. Previously, deleting the Ingress, Gateway, or LB service's Domain CR always deleted the corresponding domain in ngrok; domains created before this version keep the default Delete behavior unless explicitly changed. Developers configuring ingress domain lifecycles follow ngrok-operator changes like this on daily.dev."}},{"@type":"Question","name":"How does Argo CD show the health of ngrok Gateway API resources?","acceptedAnswer":{"@type":"Answer","text":"Starting with Argo CD v3.1.0, it reads and displays the Gateway API status conditions that ngrok-operator 0.19.0 now sets on gateways and listeners, such as a Programmed condition indicating whether the configuration was accepted and applied in ngrok's cloud. This makes debugging Gateway API configurations visible directly in the Argo CD UI. Platform engineers wiring GitOps tools to Gateway API status can find integration updates like this on daily.dev."}}]} ```