wip to add AWS #2
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
the steps here will do a full creation of the cluster, which include VPC, subnets (private and public), and security group, associating (and creating if needed) a pem, getting the endpoint and certificate to make a kube config yaml file to authenticate, and then another stack to create the workers pool. This is interesting that AWS first creates you an "empty" cluster, meaning just a control plane, and then you need to create the workers as a separate request, and apply a config map secret to the kube-system so the control plane can see the workers! This is so much more complex than GKE, and now that I have everything working to go UP I have to go backwards and figure out how to delete everything before looking into scaling... hahahahahahah aahhhhh! :) Signed-off-by: vsoch <[email protected]>
Signed-off-by: vsoch <[email protected]>
Signed-off-by: vsoch <[email protected]>
…ota increases Signed-off-by: vsoch <[email protected]>
|
The issue / error I'm running into is about network address limits - and I think it's probably safe to merge and come back to run experiments after. |
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.
The steps here will do a full creation of the cluster, which include VPC, subnets (private and public), and security group, associating (and creating if needed) a pem, getting the endpoint and certificate to make a kube config yaml file to authenticate, and then another stack to create the workers pool. This is interesting that AWS first creates you an "empty" cluster, meaning just a control plane, and then you need to create the workers as a separate request, and apply a config map secret to the kube-system so the control plane can see the workers! This is so much more complex than GKE, and now that I have everything working to go UP I have to go backwards and figure out how to delete everything before looking into scaling... hahahahahahah aahhhhh! :)