Tracked topic
… The XBackend API is experimental and its behavior can change, do not assume it is ready for production An example of a Gateway with an ExternalName backend that can be used for egress to a cloud AI API is as follows: Gateway-level TLS remains authoritative for incoming connections apiVersion : gate… …
… Apply the following manifest: --- apiVersion : v1 kind : Namespace metadata : name : gateway-infra --- apiVersion : gateway.networking.k8s.io/v1 kind : Gateway metadata : name : gateway namespace : gateway-infra spec : gatewayClassName : cloud-provider-kind listeners : - name : default hostname : "… …
… Related Kubernetes blog articles Gateway API v1.3.0: Advancements in Request Mirroring, CORS, Gateway Merging, and Retry Budgets June 2025 Gateway API v1.2: WebSockets, Timeouts, Retries, and More November 2024 Gateway API v1.1: Service mesh, GRPCRoute, and a whole lot more May 2024 New Experimenta…
… Both ListenerSets attach to the same Gateway and contribute additional HTTPS listeners. --- apiVersion : gateway.networking.k8s.io/v1 kind : Gateway metadata : name : example-gateway namespace : infra spec : gatewayClassName : example-gateway-class allowedListeners : namespaces : from : All A selec… …
I’ve just published a deep dive into Kubernetes Gateway API. The blog post covers: how Kubernetes ingress patterns evolved from Service resources to Ingress and now Gateway API why the Ingress API is limited for modern t…
I’ve published a deep dive into Kubernetes Gateway API. The blog post covers: how Kubernetes ingress patterns evolved from Service resources to Ingress and now Gateway API why the Ingress API is limited for modern teams …
Deep Dive into Kubernetes Gateway API
Deep Dive into Kubernetes Gateway API
Show HN: Krouter, a compliant Kubernetes Gateway API implementation
… The commands from the previous section output a Gateway API manifest to gwapi.yaml , and they also emit warnings that explain what did not translate exactly and what to review manually. apiVersion : gateway.networking.k8s.io/v1 kind : Gateway metadata : annotations : gateway.networking.k8s.io/gener… …
… Define GatewayClass and Gateway resources : This is a simple example, but you can find more detailed examples in this tutorial blog post for Gateway API: apiVersion: gateway.networking.k8s.io/v1beta1 kind: GatewayClass metadata: name: cilium spec: controllerName: io.cilium/gateway-controller --- ap… …
… Gateway API 1.5 is a stable release and addresses this directly. The issue is that controllers have not caught up to the spec yet. Where Gateway API goes from here Gateway API 1.5 shipped with ListenerSet, a new resource type designed to enable this separation of concerns. …
目前，AI 智能体很难尝试新的 API。智能体往往不得不浏览为人类而非为智能体设计的登录页面、联系人类添加支付方式、生成 API 密钥，最后弄清楚如何调用该 API。 智能体难以完成这个流程，有两个原因：一是缺少可用于 API 注册的稳定身份标识，二是没有原生的支付能力。因此智能体往往难以接入软件，从而制约了智能体商务的发展。AI 智能体经常完全放弃这些任务，将注册、支付方式和 API 密钥生成交还给人类。这使得智能体很难尝试和比较多个 API。 为此，我们创建了 Cloudflare Wallets。从今天开始，您可以为自己的账户 申领一个 Cloudflare Wallet 用户名 …
如今，AI 智慧體要嘗試新的 API 並不容易。它們通常得瀏覽專為人類（而非智慧體）設計的登入頁面、聯絡真人來新增付款方式、產生 API 金鑰，然後再想辦法呼叫 API。 這個流程對智慧體來說非常困難，原因有兩個：智慧體沒有穩定的識別碼來註冊 API，也沒有原生方式來支付 API 費用。因為缺乏這些，它們常常難以加入軟體服務，這限制了智慧體商務的成長。AI 智慧體經常完全放棄這些任務，把註冊、付款方式和 API 金鑰產生等工作丟回給人類。這使得智慧體很難嘗試和比較許多 API。 為了解決這個問題，我們建立了 Cloudflare Wallets。從今天起，您可以為您的帳戶 申請一個 Cl…
… Update the ClusterIssuer: Either update the current issuer or create a new one: apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: name: letsencrypt-prod spec: acme: preferredChain: "" privateKeySecretRef: name: letsencrypt-prod server: https://acme-v02.api.letsencrypt.org/directory solve… …