Add Examples Directory #40
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
We should limit configuration options to things we want users to change.
Minimal policy set to configure eks cluster with terraform. Several options are presented with comments.
That should be done by hubploy
It should work either way, but I thought it would be cleaner if all 3 nodegroup weren't managed. I also get to enable the k8s node-role this way.
This is for the UW groups' AWS resources. We have deployed an autotagging stack from GorillaStack to help us with billing. These lines help make sure Terraform tags resources the same way so that it doesn't undo changed made by the autotagging infrastructure.
Nodes are now spun up with the correct labels and taints, allowing for both autoscaling to and from 0 and spot instance usage.
Needed both of these set in order for the autoscaler to properly discover autoscaling groups.
Note: need to restrict hub.resources.requests.memory to 0.75G, or at least less than 1G
Since I changed the autotagger to put values to the 'Owner' tag, I am making the same changes here.
For me, this is us-west-2a. Others using this infrastucture on their accounts may have different zones, which is fine. The important thing is that the core node will only ever be in one zone in case you need to replace it.
|
Sorry about the commit history, I hadn't worked on |
|
I tested the |
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.
I've been doing a lot of work independent of the others on this repo and I think it's time to put it somewhere on the main branch of the repo. These are three example deployments I've done, and I'm making a new folder
aws-examples/to house them. Part of my thought process is in this issue: #39Since these are in a different folder, it shouldn't interfere with anyone's configurations. Let me know if you have thoughts @yuvipanda @jaytmiller @super-cob .