Transactions are an optional part of the API to allow change over multiple API resources atomically. Getting an entire snapshot of configuration data is quite compatible with this, since then the explicit use of…
For ideas on how to make use of the Runtime API to keep servers in a backend up-to-date dynamically, you can also take a look at a HAProxy Kubernetes Ingress Controller implementation that makes use of it here…
Kubernetes Ingress Controllers for HAProxy already exist. A nice one is at https://github.com/jcmoraisjr/haproxy-ingress Other examples of usage are spread around in the examples section of the ingress repo, like here…
Transactions are an optional part of the API to allow change over multiple API resources atomically. Getting an entire snapshot of configuration data is quite compatible with this, since then the explicit use of…
For ideas on how to make use of the Runtime API to keep servers in a backend up-to-date dynamically, you can also take a look at a HAProxy Kubernetes Ingress Controller implementation that makes use of it here…
Kubernetes Ingress Controllers for HAProxy already exist. A nice one is at https://github.com/jcmoraisjr/haproxy-ingress Other examples of usage are spread around in the examples section of the ingress repo, like here…