You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here https://github.com/gardener/dashboard/blob/master/docs/development/local-setup.md#3-configuration
In this step it instructs to place the Gardener Dashboard configuration under ${HOME}/.gardener/config.yaml or alternatively set the path to the configuration file using the GARDENER_CONFIG environment variable.
But as far as I observed this specific file i.e config.yaml is not being generated by gardener at this location.
I believe there is a need to update the instructions.
The text was updated successfully, but these errors were encountered:
The config file contains the Dashboard configuration. It is not generated by Gardener or the Dashboard. You need to place it in .gardener folder or define the path using the mentioned environment variable. It contains all configuration options for the Gardener Dashboard most of them are optional.
The local setup documentation contains only minimal configuration options. Check the helm charts for more configuration options.
Hi @grolu , it is understandable that it is not generated by Gardener or the Dashboard. But I find myself a bit lost in the setup process.
I've been trying to use Dashboard for the Gardener which I've set up locally using a KinD cluster. Can you please point me to some resource or suggest steps to follow. Thanks.
Here https://github.com/gardener/dashboard/blob/master/docs/development/local-setup.md#3-configuration
In this step it instructs to place the Gardener Dashboard configuration under ${HOME}/.gardener/config.yaml or alternatively set the path to the configuration file using the GARDENER_CONFIG environment variable.
But as far as I observed this specific file i.e config.yaml is not being generated by gardener at this location.
I believe there is a need to update the instructions.
The text was updated successfully, but these errors were encountered: