<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>WG AI Gateway on Kubernetes Contributors</title><link>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/ai-gateway/</link><description>Recent content in WG AI Gateway on Kubernetes Contributors</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/ai-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>WG AI Gateway Charter</title><link>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/ai-gateway/charter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/ai-gateway/charter/</guid><description>&lt;h1 id="wg-ai-gateway-charter">WG AI Gateway Charter&lt;/h1>
&lt;p>This charter adheres to the conventions described in the &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md"
 
 target="_blank" rel="noopener">Kubernetes Charter
README&lt;/a>
 and uses the Roles and Organization Management outlined in
&lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md"
 
 target="_blank" rel="noopener">wg-governance&lt;/a>
.&lt;/p>
&lt;h2 id="background">Background&lt;/h2>
&lt;p>We’ve seen large growth in the number of “AI Gateways” that have been launched
in the last couple of years which deploy and operate on Kubernetes, often
utilizing Gateway API. This WG aims to determine if the relevant features have
staying power and will be commonly useful to users for years to come, and if we
should expand the Kubernetes standards around this.&lt;/p></description></item></channel></rss>