Skip to content
This repository has been archived by the owner on Jul 25, 2022. It is now read-only.

Logs for controlplane components should not require a shoot to be targeted #436

Closed
dansible opened this issue Nov 10, 2020 · 3 comments · Fixed by #471
Closed

Logs for controlplane components should not require a shoot to be targeted #436

dansible opened this issue Nov 10, 2020 · 3 comments · Fixed by #471
Assignees

Comments

@dansible
Copy link
Contributor

dansible commented Nov 10, 2020

When getting logs for the apiserver, etcd, and other control plane components, gardenctl requires you to have a shoot targeted. If users are already targeting the controlplane, it should be possible to get logs for anything running on the seed without needing to target a shoot

List of logging components on the seed:

  • gardener-controller-manager existing logic doesn't require shoot to be targeted for gardener-controller-manager
  • kube-apiserver done
  • kube-scheduler done
  • kube-controller-manager done
  • etcd-main done
  • etcd-events done
  • vpn-seed done
  • machine-controller-manager done
  • prometheus done
  • gardenlet done
  • cluster-autoscaler done
  • tf
@neo-liang-sap
Copy link
Contributor

/assign

@neo-liang-sap
Copy link
Contributor

will work on this one after #437 close

@neo-liang-sap
Copy link
Contributor

tf issue fixed in comments #470

Gardenctl Backlog automation moved this from In progress to Done Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants