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
As you can see from the screenshot, the Config Path column is blank. Since adding the support for multi-region K8s provider configurations, we store the kubeconfig at the region level instead of at the provider level. Solution might be to remove this column or add additional layout elements to display each region's kubeconfig.
Summary:
Show region level config paths for k8s providers
{F14952}
Test Plan:
1) Run UI
2) Open Managed Kubernetes Service tab at Configs
3) Observe Config Path column filled with data
Reviewers: andrew
Reviewed By: andrew
Subscribers: jenkins-bot, yugaware, ui
Differential Revision: https://phabricator.dev.yugabyte.com/D10526
polarweasel
pushed a commit
to lizayugabyte/yugabyte-db
that referenced
this issue
Mar 9, 2021
…roviders
Summary:
Show region level config paths for k8s providers
{F14952}
Test Plan:
1) Run UI
2) Open Managed Kubernetes Service tab at Configs
3) Observe Config Path column filled with data
Reviewers: andrew
Reviewed By: andrew
Subscribers: jenkins-bot, yugaware, ui
Differential Revision: https://phabricator.dev.yugabyte.com/D10526
As you can see from the screenshot, the
Config Path
column is blank. Since adding the support for multi-region K8s provider configurations, we store the kubeconfig at the region level instead of at the provider level. Solution might be to remove this column or add additional layout elements to display each region's kubeconfig.@Arnav15 What do you think?
The text was updated successfully, but these errors were encountered: