You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+7
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
[3.0.0] - 2020-01-22
9
9
10
+
## Added
11
+
12
+
- The type of the Kubernetes cluster can no be specified.
13
+
Set this to `eks` if targeting a managed [EKS](https://aws.amazon.com/eks/) Cluster.
14
+
- If targeting EKS clusters, pods will use IAM roles for service accounts](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html)
15
+
as intended by AWS.
16
+
10
17
## Updated
11
18
12
19
- The default version of the controller has been set to [v1.1.5](https://github.com/kubernetes-sigs/aws-alb-ingress-controller/releases/tag/v1.1.5)
Copy file name to clipboardexpand all lines: README.md
+10
Original file line number
Diff line number
Diff line change
@@ -2,3 +2,13 @@
2
2
3
3
This Terraform module can be used to install the [AWS ALB Ingress Controller](https://github.com/kubernetes-sigs/aws-alb-ingress-controller)
4
4
into a Kubernetes cluster.
5
+
6
+
## Improved integration with Amazon Elastic Kubernetes Service (EKS)
7
+
8
+
This module can be used to install the ALB Ingress controller into a "vanilla" Kubernetes cluster (which is the default)
9
+
or it can be used to integrate tightly with AWS-managed [EKS](https://aws.amazon.com/eks/) clusters which allows the deployed pods to
10
+
[use IAM roles for service accounts](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html).
11
+
12
+
It is required, that an OpenID connect provider [has already been created](https://www.terraform.io/docs/providers/aws/r/eks_cluster.html#example-iam-role-for-eks-cluster) for your EKS cluster for this feature to work.
13
+
14
+
Just make sure that you set the variable `k8s_cluster_type` type if running on EKS.
Copy file name to clipboardexpand all lines: variables.tf
+11-2
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
variable"k8s_cluster_type" {
2
+
description="Can be set to `vanilla` or `eks`. If set to `eks`, the Kubernetes cluster will be assumed to be run on EKS which will make sure that the AWS IAM Service integration works as supposed to."
3
+
type=string
4
+
default="vanilla"
5
+
}
6
+
1
7
variable"k8s_cluster_name" {
2
8
description="Name of the Kubernetes cluster. This string is used to contruct the AWS IAM permissions and roles."
3
9
type=string
@@ -11,14 +17,17 @@ variable "k8s_namespace" {
11
17
variable"aws_iam_path_prefix" {
12
18
description="Prefix to be used for all AWS IAM objects."
0 commit comments