-
Notifications
You must be signed in to change notification settings - Fork 1
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
Use cluster name for resource creation #3
Comments
Alright, I can make |
Thanks! What do mean as environment? The AWS region or the |
By "environment", I meant dev, int, test, stage and prod from a development sense.
Generally speaking that's true but every so often |
I see, in our use case at least, it's possible to have multiple clusters for different customers.
Fair enough, I think that would be a manual and one in a while process and not a continuous bucket sharing of a 2 different prod clusters. |
Indeed, continuous bucket sharing probably needs prefixes for organising objects belonging to different clusters. The ${var.environment} is now removed from resource names and only used in DNS names and as cost-allocation tags. #7 |
Closed by #7. |
S3 bucket names should be globally unique, values commonly used in
${var.environment}
such asdev
andprod
won't be unique.Edit:
${var.environment}
is used in other places as well. I think its description and examples can be improved to suggest that it's name of the environment in general and not whether it's dev or prod. Or the value to be merged with${var.eks_cluster_name}
.The text was updated successfully, but these errors were encountered: