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
@neo-liang-sap

Comments

@dansible
Copy link
Contributor

dansible commented Nov 10, 2020 •
edited by neo-liang-sap
Loading

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 neo-liang-sap mentioned this issue Nov 26, 2020
Merged
@tedteng tedteng mentioned this issue Dec 1, 2020
Open
@neo-liang-sap
Copy link
Contributor

tf issue fixed in comments #470

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@neo-liang-sap neo-liang-sap

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

enable gardenctl logs for some components while targeting the control plane neo-liang-sap/gardenctl
2 participants
@dansible @neo-liang-sap