Support k8gb behind a reverse proxy #1710
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Andre Baptista Aguas <[email protected]>
abaguas
requested review from
donovanmuller,
k0da,
kuritka,
ytsarev and
jkremser
as code owners
Problem
K8GB reads IP addresses from `Ingress.Status.LoadBalancer.Ingress` or from `Service.Status.LoadBalancer.Ingress` for ingress configured with Kubernetes Ingress and Istio Virtual Service, respectively.
The IP addresses exposed by these resources are the IP addresses exposed by the Kubernetes Cluster. However, in some setups the clients do not route their traffic to these IP addresses because the cluster is behind a reverse proxy.
Solution
To support this setup, K8GB should expose DNS records with the IP address of the reverse proxy. Since the address is unknown to the cluster the K8GB administrator must provide it via configuration. This PR adds to K8GB the capability to read IP address from an annotation `k8gb.io/external-ips` on Ingress and Service resources.
Examples
```
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
labels:
app: ingress
annotations:
k8gb.io/external-ips: "185.199.110.153"
```
```
apiVersion: v1
kind: Service
metadata:
name: istio-ingressgateway
namespace: istio-ingress
labels:
app: istio-ingressgateway
annotations:
k8gb.io/external-ips: "185.199.110.153,185.199.109.153"
```
Fixes k8gb-io#1275
Signed-off-by: Andre Baptista Aguas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
K8GB reads the IP addresses it exposes from
Ingress.Status.LoadBalancer.Ingressor fromService.Status.LoadBalancer.Ingressfor ingresses configured with Kubernetes Ingress or Istio Virtual Service, respectively.However, in some setups the clients do not route their traffic to these IP addresses because the cluster is behind a reverse proxy.
Solution
To support this setup, K8GB should expose DNS records with the IP address of the reverse proxy. Since the address is unknown to the cluster the K8GB administrator must provide it via configuration. This PR adds to K8GB the capability to read IP address from an annotation
k8gb.io/exposed-ip-addresseson Ingress and Service resources.Examples
Fixes #1275