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
1. What kops version are you running? The command kops version, will display
this information.
master
2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.
1.11.6
3. What cloud provider are you using?
openstack
4. What commands did you run? What is the simplest way to reproduce this issue?
After cluster is up and running, each instance hostname is same called oma.
6. What did you expect to happen?
I except that each instance should have its own exact same hostname that exist in cloudprovider api (in this case openstack). Example: oma.k8s.local-master-nova-1-1 or oma.k8s.local-master-nova-2-1 and so on. Should we insert this to cloud-init?
/kind bug
The text was updated successfully, but these errors were encountered:
1. What
kops
version are you running? The commandkops version
, will displaythis information.
master
2. What Kubernetes version are you running?
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.1.11.6
3. What cloud provider are you using?
openstack
4. What commands did you run? What is the simplest way to reproduce this issue?
5. What happened after the commands executed?
After cluster is up and running, each instance hostname is same called
oma
.6. What did you expect to happen?
I except that each instance should have its own exact same hostname that exist in cloudprovider api (in this case openstack). Example:
oma.k8s.local-master-nova-1-1
oroma.k8s.local-master-nova-2-1
and so on. Should we insert this to cloud-init?/kind bug
The text was updated successfully, but these errors were encountered: