Feature/ k8s-eks-v1.17 layer tested #398
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… with new dir name related path
… fix lack of AWS EKS web console permissions
…void getting eks "nodeGroupName can't be longer than 63 characters!" error + NACL to allow vault hvn peering traffic
…e private ingress
… to shared centralized definition
…h us-east-1 stack
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Commits on Jun 29, 2022
apps-devstg/us-east-1/k8s-eks-v1.17 config.tf files state key updated with new dir name related path - @exequielrafaela
apps-devstg/us-east-1/k8s-eks-v1.17/cluster adding DevOps SSO role to fix lack of AWS EKS web console permissions - @exequielrafaela
minor sintaxt, spaces and comments updates - @exequielrafaela
Updating cluster_name with version sufix and short 1ry reference to avoid getting eks "nodeGroupName can't be longer than 63 characters!" error + NACL to allow vault hvn peering traffic - @exequielrafaela
apps-devstg/us-east-1/k8s-eks-v1.17/k8s-resources k8s dashboard to use private ingress - @exequielrafaela
apps-devstg/us-east-1/k8s-eks-v1.17/network removing peering in favor to shared centralized definition - @exequielrafaela
apps-devstg/us-east-1/k8s-eks-v1.17 README.md - @exequielrafaela
apps-devstg/us-east-2/k8s-eks-v1.17 folder renamed + sync changes with us-east-1 stack - @exequielrafaela
shared/us-east-2/base-network lock file added - @exequielrafaela
Why?
Consideration
Screenshots