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

Clustername #35

Merged
merged 2 commits into from
May 9, 2019
Merged

Clustername #35

merged 2 commits into from
May 9, 2019

Conversation

andyz-dev
Copy link
Contributor

Attempt to properly fix the bug mentioned in #34

To ensure all reference of the default cluster name are the same.
Not having to check for typos will make it easier to maintain.
Copy link
Member

@iwilltry42 iwilltry42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR!
I just left some small comments, but nothing too bad 👍

cli/commands.go Outdated Show resolved Hide resolved
cli/commands.go Show resolved Hide resolved
cli/commands.go Show resolved Hide resolved
MAke sure the cluster name is a RFC 1123 compliant host name, since the
cluster name is used as base for expanding into a auto generated
host names for k3s nodes.
Copy link
Member

@iwilltry42 iwilltry42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@iwilltry42 iwilltry42 merged commit 4c14a8e into k3d-io:master May 9, 2019
@andyz-dev andyz-dev deleted the clustername branch May 9, 2019 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants