Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Support Amazon EKS Managed Node Groups #10915

Closed
bflad opened this issue Nov 18, 2019 · 3 comments · Fixed by #10916
Closed

Feature Request: Support Amazon EKS Managed Node Groups #10915

bflad opened this issue Nov 18, 2019 · 3 comments · Fixed by #10916
Labels
new-resource Introduces a new resource. service/eks Issues and PRs that pertain to the eks service.
Milestone
v2.38.0

Comments

@bflad
Copy link
Contributor

bflad commented Nov 18, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Today, AWS has announced the release of Managed Node Groups for Amazon EKS. HashiCorp is proud to announce launch day support for this feature in Terraform. The Managed Node Groups functionality allows automated management of Kubernetes worker nodes by creating, updating, and deleting an Auto Scaling Group (ASG) with EKS compatible Kubernetes software and configuration pre-installed on nodes. Previously, worker node ASGs and any updates would need to be configured and performed manually.

Available in version 2.38.0 of the Terraform AWS Provider, a new aws_eks_node_group resource can manage this new functionality. The resource documentation can be found on the Terraform website. EKS and the new Terraform resource support in-place updates for EKS Amazon Machine Image (AMI) updates, which can automatically be deployed across nodes while respecting Kubernetes Pod Disruption Budgets.

New Resource(s)

  • aws_eks_node_group

Potential Terraform Configuration

resource "aws_eks_node_group" "example" {
  cluster_name    = aws_eks_cluster.example.name
  node_group_name = "example"
  node_role_arn   = aws_iam_role.example.arn
  subnet_ids      = aws_subnet.example[*].id

  scaling_config {
    desired_size = 1
    max_size     = 1
    min_size     = 1
  }
}

References
@bflad bflad added new-resource Introduces a new resource. service/eks Issues and PRs that pertain to the eks service. labels Nov 18, 2019
@bflad bflad added this to the v2.38.0 milestone Nov 18, 2019
@bflad bflad mentioned this issue Nov 18, 2019
Merged
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Nov 18, 2019
@bflad bflad removed the needs-triage Waiting for first response or review from a maintainer. label Nov 18, 2019
@bflad
Copy link
Contributor Author

bflad commented Nov 18, 2019

The functionality has been merged and will release in version 2.38.0 of the Terraform AWS Provider, shortly. 🚀

@ghost
Copy link

ghost commented Nov 18, 2019

This has been released in version 2.38.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

bflad added a commit that referenced this issue Nov 18, 2019
@bflad
examples/eks-getting-started: Update for new EKS Node Group functiona…
a44d601 
…lity

Reference: https://aws.amazon.com/blogs/containers/eks-managed-node-groups/
Reference: #10915

Example output:

```
$ terraform apply
Apply complete! Resources: 18 added, 0 changed, 0 destroyed.
$ aws eks update-kubeconfig --name terraform-eks-demo
$ kubectl get nodes
NAME                                       STATUS   ROLES    AGE     VERSION
ip-10-0-0-133.us-west-2.compute.internal   Ready    <none>   6m40s   v1.14.7-eks-1861c5
```
@bflad bflad mentioned this issue Nov 18, 2019
Merged
@wmorgan6796 wmorgan6796 mentioned this issue Nov 19, 2019
Closed
3 tasks
@ewbankkit ewbankkit mentioned this issue Nov 19, 2019
Closed
bflad added a commit that referenced this issue Nov 21, 2019
@bflad
examples/eks-getting-started: Update for new EKS Node Group functiona…
cfe6564 
…lity (#10918)

Reference: https://aws.amazon.com/blogs/containers/eks-managed-node-groups/
Reference: #10915

Example output:

```
$ terraform apply
Apply complete! Resources: 18 added, 0 changed, 0 destroyed.
$ aws eks update-kubeconfig --name terraform-eks-demo
$ kubectl get nodes
NAME                                       STATUS   ROLES    AGE     VERSION
ip-10-0-0-133.us-west-2.compute.internal   Ready    <none>   6m40s   v1.14.7-eks-1861c5
```
pixelpogo pushed a commit to babbel/terraform-provider-aws that referenced this issue Nov 22, 2019
@bflad @pixelpogo
examples/eks-getting-started: Update for new EKS Node Group functiona…
a00e0bd 
…lity (hashicorp#10918)

Reference: https://aws.amazon.com/blogs/containers/eks-managed-node-groups/
Reference: hashicorp#10915

Example output:

```
$ terraform apply
Apply complete! Resources: 18 added, 0 changed, 0 destroyed.
$ aws eks update-kubeconfig --name terraform-eks-demo
$ kubectl get nodes
NAME                                       STATUS   ROLES    AGE     VERSION
ip-10-0-0-133.us-west-2.compute.internal   Ready    <none>   6m40s   v1.14.7-eks-1861c5
```
iffyuva pushed a commit to dockup/terraform-aws that referenced this issue Nov 25, 2019
@bflad
examples/eks-getting-started: Update for new EKS Node Group functiona…
9eb0727 
…lity (#10918)

Reference: https://aws.amazon.com/blogs/containers/eks-managed-node-groups/
Reference: hashicorp/terraform-provider-aws#10915

Example output:

```
$ terraform apply
Apply complete! Resources: 18 added, 0 changed, 0 destroyed.
$ aws eks update-kubeconfig --name terraform-eks-demo
$ kubectl get nodes
NAME                                       STATUS   ROLES    AGE     VERSION
ip-10-0-0-133.us-west-2.compute.internal   Ready    <none>   6m40s   v1.14.7-eks-1861c5
```
@ghost
Copy link

ghost commented Mar 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
new-resource Introduces a new resource. service/eks Issues and PRs that pertain to the eks service.
Projects
None yet
Milestone
v2.38.0
Development

Successfully merging a pull request may close this issue.

New Resource: aws_eks_node_group hashicorp/terraform-provider-aws
1 participant
@bflad