Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kube: add kube_public_addr config field to proxy_service #5611

Merged
merged 2 commits into from
Feb 18, 2021

Conversation

awly
Copy link
Contributor

@awly awly commented Feb 17, 2021

With the introduction of kube_listen_addr, some users are confused on
how to set a public address for k8s access that's different from
public_addr of the proxy. kube_public_addr removes that confusion
and more closely resembles the other proxy endpoints.

This config:

proxy_service:
  kube_listen_addr: 0.0.0.0:3026
  kube_public_addr: kube.example.com:3026

translates to the old format:

proxy_service:
  kubernetes:
    enabled: yes
    listen_addr: 0.0.0.0:3026
    public_addr: kube.example.com:3026

Fixes #5110

With the introduction of `kube_listen_addr`, some users are confused on
how to set a public address for k8s access that's different from
`public_addr` of the proxy. `kube_public_addr` removes that confusion
and more closely resembles the other proxy endpoints.

This config:

```yaml
proxy_service:
  kube_listen_addr: 0.0.0.0:3026
  kube_public_addr: kube.example.com:3026
```

translates to the old format:

```yaml
proxy_service:
  kubernetes:
    enabled: yes
    listen_addr: 0.0.0.0:3026
    public_addr: kube.example.com:3026
```
@awly awly merged commit e1e8063 into master Feb 18, 2021
@awly awly deleted the andrew/kube_public_addr branch February 18, 2021 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add proxy_service.kube_public_addr field in teleport.yaml
3 participants