You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you using this to proxy access to your public k8s API?
In our case, we have customers that will be using our k8s API server (i.e. we are a multi-tenant, multi-cluster cloud provider) but in addition to having a proxy/gateway in front of Prom, Grafana, et al., we also want to put the k8s API server behind the proxy (for public access/consumption; internal apiserver traffic can still go directly to the internal service).
So I have 2 questions:
Does this sound like a reasonable idea?
How are you provisioning TLS client certificates for the client-server authentication? e.g. when setting up k8s authenticating proxy one is required to configure an API server param --requestheader-client-ca-file=/path/to/client/ca/file. I imagine this pattern has showed up in your proxying patterns somewhere so I am curious if you've written any software to automate it.
The text was updated successfully, but these errors were encountered:
Hello there, nice project! 👋
Are you using this to proxy access to your public k8s API?
In our case, we have customers that will be using our k8s API server (i.e. we are a multi-tenant, multi-cluster cloud provider) but in addition to having a proxy/gateway in front of Prom, Grafana, et al., we also want to put the k8s API server behind the proxy (for public access/consumption; internal apiserver traffic can still go directly to the internal service).
So I have 2 questions:
--requestheader-client-ca-file=/path/to/client/ca/file
. I imagine this pattern has showed up in your proxying patterns somewhere so I am curious if you've written any software to automate it.The text was updated successfully, but these errors were encountered: