Skip to content

[v13] Fix Kubernetes Legacy Proxy heartbeats#29738

Merged
tigrato merged 2 commits intobranch/v13from
bot/backport-29733-branch/v13
Jul 28, 2023
Merged

[v13] Fix Kubernetes Legacy Proxy heartbeats#29738
tigrato merged 2 commits intobranch/v13from
bot/backport-29733-branch/v13

Conversation

@tigrato
Copy link
Copy Markdown
Contributor

@tigrato tigrato commented Jul 28, 2023

Backport #29733 to branch/v13

tigrato added 2 commits July 28, 2023 16:23
When a Teleport Kubernetes Proxy runs in legacy mode - i.e. - spec
enables `proxy_service.kubernetes.enabled`, the proxy is capable of
proxy requests to a target Kubernetes cluster instead of forwarding them
to a Teleport Kubernetes Service.

The following config enables the legacy proxy mode in proxy:

```yaml
proxy_service:
    enabled: yes
    web_listen_addr: 0.0.0.0:3080
    public_addr: tele.local:3080
    kubernetes:
      enabled: yes
      listen_addr: 0.0.0.0:3026
      kubeconfig_file: path # optional
```

Because the proxy forwards and heartbeat the configured Kube clusters,
it needs permissions to upsert the kube cluster in auth's backend and
to extend its expiration date.

This PR fixes a problem that exists since Teleport 8 where the proxy
is allowed to upsert the kube server but it's not allowed to extend the
expiration time.

When the request fails, the proxy becomes in degraded state and the
performance is affected.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
@tigrato tigrato added this pull request to the merge queue Jul 28, 2023
Merged via the queue into branch/v13 with commit a21f6c8 Jul 28, 2023
@tigrato tigrato deleted the bot/backport-29733-branch/v13 branch July 28, 2023 17:02
@fheinecke fheinecke mentioned this pull request Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants