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

Improve documentation for users on how to setup and configure gardenctl #472

Open
6 tasks
dansible opened this issue Nov 26, 2020 · 2 comments
Open
6 tasks
Labels
lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@dansible
Copy link
Contributor

dansible commented Nov 26, 2020

It would be great to add some more documentation for end users (specifically non-admins) for how they can setup and use gardenctl. Some of the topics:

  • General explanation of the Gardener components and how they relate to one another (can be links to existing documentation) -> Garden (Soil) / Project / Namespace / Shoot
  • Downloading your OIDC-kubeconfig (or service account kubeconfig)
  • Setup ~/.garden/config to point to the kubeconfig
  • How to target your garden
  • What you have access to in your project (clarify what is a project vs namespace)
  • How to target your shoot
@uvwild
Copy link

uvwild commented Nov 26, 2020

### Me too:

  • I can configure .garden/config with the clusters.

But all I can do is gardenctl ls gardens (which shows the entries from the cluster in the config)

Trying to list any other resource gardenctl ls XXXX
returns
Error: the server could not find the requested resource (get XXX.core.gardener.cloud)
(with XXX in projects, seeds,shoots,issues,namespaces)

There is some essential information missing explaining the configuration!

When I try targeting I get
gardenctl -d target --server https://api.ing.garden.otcdemo.gardener.t-systems.net --seed otc-seed --namespace shoot--openedx--openedx
a garden could not be matched for the provided server address: https://serveraddress/

However, curl -l https://serveraddress gives me the API Server

@petersutter
Copy link
Contributor

petersutter commented Nov 26, 2020

@uvwild The kubeconfig that you use for the garden config must be the (virtual) garden cluster. It's the cluster that exposed the Project, Shoot, Seed etc. resources

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 22, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

4 participants