Terraform AWS article #305
Open
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
| export const TerraformAWS = { | ||
| id: 'terraform-aws', | ||
| url: '/terraform-aws', | ||
| title: 'Bootstrapping Kubernetes clusters on AWS with Terraform', |
There was a problem hiding this comment.
- Automating Kubernetes cluster provisioning for testing
- How to automate Kubernetes cluster provisioning
- Provisioning Kubernetes clusters at scale for feature testing
- Testing Kubernetes at scale with a custom installer
- Building a custom Kubernetes installer
|
|
||
| The aim of the project is to enable the creation of disposable kubeadm clusters which is an enabler for running controlled and automated Kubernetes experiments. | ||
|
|
||
| _The remainder of this article first reviews the available options for creating Kubernetes clusters and then presents the Terraform module._ |
There was a problem hiding this comment.
I think you could add a link to the repo here. I know it was linked above, but it's not clear that is something that you built. I'd say something along the lines of:
And if you want to jump to the code ...
src/terraform-aws/content.md
Outdated
|
|
||
| _They allow you to use Kubernetes in a Software as a Service (SaaS) manner._ | ||
|
|
||
| Naturally, managed Kubernetes services provide the highest degree of automation (creation and operation are entirely done for you), but the least amount of flexibility (you can configure only those settings that the service provider exposes through its API). |
src/terraform-aws/content.md
Outdated
|
|
||
| ## Managed Kubernetes services | ||
|
|
||
| Generally, the options for creating a Kubernetes cluster can be divided into two categories: managed services and installation tools. |
|
|
||
| ## Kubernetes installation tools | ||
|
|
||
| Kubernetes installation tools allow you to install Kubernetes on your own infrastructure (both on-premises or in the cloud). |
|
|
||
| In the present configuration, all clusters use the same settings, but you could configure each cluster separately by specifying different [input variales](https://registry.terraform.io/modules/weibeld/kubeadm/aws?tab=inputs) for the individual invocations of the kubeadm module. | ||
|
|
||
| > You could also create a dedicated VPC for each cluster by adding additional invocations of the network submodule. |
There was a problem hiding this comment.
This should change if you drop the previous chapter and should be a link to the docs.
| terraform apply | ||
| ``` | ||
|
|
||
| If you pay attention to the execution plan that Terraform presents to you, you should see that it includes the creation of the resources belonging to two new clusters. |
There was a problem hiding this comment.
plan that Terraform presents to you
|
|
||
| If you pay attention to the execution plan that Terraform presents to you, you should see that it includes the creation of the resources belonging to two new clusters. | ||
|
|
||
| This means, that Terraform will create two new clusters while leaving the existing cluster unchanged — that's because you just added two new cluster specifications in your configuration, but didn't modify the existing one. |
src/terraform-aws/content.md
Outdated
|
|
||
| ## Installing CNI plugins | ||
|
|
||
| You have three clusters now, but something might still itch you about them. |
There was a problem hiding this comment.
You have three clusters now, but all of them are incomplete.
src/terraform-aws/content.md
Outdated
|
|
||
| _The CNI plugins indeed completed the setup of your clusters and rendered them fully functional._ | ||
|
|
||
| At this point, you can launch further Pods in your clusters and do any other kinds of experiments. |
There was a problem hiding this comment.
and do any other kinds of experiments.
and do more experiments.
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.
Preview: https://deploy-preview-305--learnk8s.netlify.app/blog