<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Alek&#x27;s Blog - xds</title>
    <subtitle>Production notes on Kubernetes, OpenShift, and OVHcloud: observability, log archiving, service mesh, LLM inference, and digital sovereignty.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://blog.none.at/tags/xds/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://blog.none.at"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-04-19T00:00:00+00:00</updated>
    <id>https://blog.none.at/tags/xds/atom.xml</id>
    <entry xml:lang="en">
        <title>Envoy Gateway v1.7: Global Rate Limiting with a Custom ratelimit Service</title>
        <published>2026-04-19T00:00:00+00:00</published>
        <updated>2026-04-19T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              aleks
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.none.at/blog/2026/2026-04-19-envoy-gateway-global-ratelimit/"/>
        <id>https://blog.none.at/blog/2026/2026-04-19-envoy-gateway-global-ratelimit/</id>
        
        <summary type="html">&lt;p&gt;Global rate limiting in &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;gateway.envoyproxy.io&#x2F;&quot;&gt;Envoy Gateway (EG)&lt;&#x2F;a&gt; can be set up in two ways:
the easy path (EG manages its own &lt;code&gt;envoy-ratelimit&lt;&#x2F;code&gt; container) and the flexible path
(you bring your own &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;envoyproxy&#x2F;ratelimit&quot;&gt;envoyproxy&#x2F;ratelimit&lt;&#x2F;a&gt; service).
This post covers the flexible path — &lt;strong&gt;Option B&lt;&#x2F;strong&gt; — and documents the three xDS patches
required to wire it up, the EG v1.7 breaking changes that affect the approach,
and a namespace-admin self-service deployment model.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
