Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add random prefix to components #60

Open
clstokes opened this issue Jan 25, 2018 · 0 comments
Open

Add random prefix to components #60

clstokes opened this issue Jan 25, 2018 · 0 comments

Comments

@clstokes
Copy link

clstokes commented 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.

$ 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
@clstokes clstokes changed the title Add random prefix or suffix to components Add random prefix to components Jan 25, 2018
aegixx added a commit to aegixx/triton-kubernetes that referenced this issue Mar 22, 2018
aegixx added a commit to aegixx/triton-kubernetes that referenced this issue Mar 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants