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

Kubernetes Enhancements #3952

Closed
14 of 16 tasks
russjones opened this issue Jun 30, 2020 · 1 comment
Closed
14 of 16 tasks

Kubernetes Enhancements #3952

russjones opened this issue Jun 30, 2020 · 1 comment

Comments

@russjones
Copy link
Contributor

russjones commented Jun 30, 2020

RFD: #4455

  • add kubernetes_service to teleport.yaml
  • add kube_listen_addr to proxy_service
  • reverse tunnels (IoT mode) for kubernetes_service
  • k8s proxy request routing to kubernetes_service
  • support multiple clusters in kubeconfig
  • RBAC for k8s
    • labels on k8s clusters
    • kubernetes_labels filter on roles
  • complete k8s audit logs (all requests)
  • tsh
    • list/switch clusters
    • exec plugin for kubectl
  • register k8s clusters handled by proxies
  • helm one-liner to deploy proxy in k8s cluster
  • migration guide
  • update test plan
@russjones russjones added this to the 5.0 Codename TBD milestone Jun 30, 2020
awly pushed a commit that referenced this issue Sep 21, 2020
Cluster name from this field plug all clusters from kubeconfig are
stored on the auth server via heartbeats.
This info will later be used to route k8s requests back to proxies.

Updates #3952
awly pushed a commit that referenced this issue Sep 24, 2020
Cluster name from this field plug all clusters from kubeconfig are
stored on the auth server via heartbeats.
This info will later be used to route k8s requests back to proxies.

Updates #3952
awly pushed a commit that referenced this issue Sep 29, 2020
Cluster name from this field plug all clusters from kubeconfig are
stored on the auth server via heartbeats.
This info will later be used to route k8s requests back to proxies.

Updates #3952
awly pushed a commit that referenced this issue Sep 30, 2020
Cluster name from this field plug all clusters from kubeconfig are
stored on the auth server via heartbeats.
This info will later be used to route k8s requests back to proxies.

Updates #3952
@awly
Copy link
Contributor

awly commented Nov 13, 2020

All core functionality is in. Remaining tasks are docs and deployment tooling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants