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
Some cloud providers require unique names for certain components and this can cause collisions and failed deployments if users enter commonly used names for their cluster names. The deployment should add a random prefix to components on deployment. This value should be consistent across all components and providers for the same global cluster.
e.g.
$ triton ls
SHORTID NAME IMG STATE FLAGS AGE
224569d6 fda-312-clstokes-master-1 ubuntu-certified-16.04@20180109 running K 17h
afb6ee91 fda-312-etcd-1 ubuntu-certified-16.04@20180109 running K 17h
56e1d04a fda-312-node-2 ubuntu-certified-16.04@20180109 running K 17h
55d0624b fda-312-node-1 ubuntu-certified-16.04@20180109 running K 17h
96d4a1de fda-312-node-4 ubuntu-certified-16.04@20180109 running K 16h
f815fb11 fda-312-node-3 ubuntu-certified-16.04@20180109 running K 16h
The text was updated successfully, but these errors were encountered:
clstokes
changed the title
Add random prefix or suffix to components
Add random prefix to components
Jan 25, 2018
Some cloud providers require unique names for certain components and this can cause collisions and failed deployments if users enter commonly used names for their cluster names. The deployment should add a random prefix to components on deployment. This value should be consistent across all components and providers for the same global cluster.
e.g.
The text was updated successfully, but these errors were encountered: