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
{{ message }}
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
What happened:
IHAC who is starting up with Kubernetes running on vSphere. They have a concerns as while configuring K8 cluster user need to specify the datastore manually for every deployment. As the environment grows if later at any point they need to re-point it to a different datastore then how this will happen? Also is there any possibility of pointing K8 cluster to vSphere Storage Cluster instead of specifying datastore which can make the process simpler.
What you expected to happen:
I need help on this query how to address it
How to reproduce it (as minimally and precisely as possible):
This is default behavior of K8 cluster
Anything else we need to know?:
NA
Environment:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
@sidharthswami This is a known issue also tracked by #471 and #203. This feature may not be implememted in the near future due to our current tight schedule. @tusharnt
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
IHAC who is starting up with Kubernetes running on vSphere. They have a concerns as while configuring K8 cluster user need to specify the datastore manually for every deployment. As the environment grows if later at any point they need to re-point it to a different datastore then how this will happen? Also is there any possibility of pointing K8 cluster to vSphere Storage Cluster instead of specifying datastore which can make the process simpler.
What you expected to happen:
I need help on this query how to address it
How to reproduce it (as minimally and precisely as possible):
This is default behavior of K8 cluster
Anything else we need to know?:
NA
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: