Terraform module to provision an EKS Fargate Profiles for Elastic Container Service for Kubernetes.
Based on Terraform Resource
Here's the gist of using it directly from github.
module "eks_fargate" {
source = "terraform-module/eks-fargate-profile/aws"
version = "2.2.0"
cluster_name = "my-cluster-name"
subnet_ids = ["subnet-xxx"]
namespaces = ["default"]
labels = {
"app.kubernetes.io/name" = "default-service"
}
tags = {
"ENV" = "dev"
}
}
Name | Version |
---|---|
terraform | >= 0.12.2 |
aws | >= 2.5 |
Name | Version |
---|---|
aws | >= 2.5 |
Name | Description | Type | Default | Required |
---|---|---|---|---|
cluster_name | Cluster name | string |
n/a | yes |
labels | Key-value mapping of Kubernetes labels for selection | map(string) |
{} |
no |
namespaces | Kubernetes namespace(s) for selection. Adding more than one namespace, creates and manages multiple namespaces. | list(string) |
n/a | yes |
prefix | Prefix added to the name. In case your cluster name begins with a reserved string (e.g. eks- ). |
string |
"" |
no |
subnet_ids | Identifiers of private EC2 Subnets to associate with the EKS Fargate Profile. These subnets must have the following resource tag: kubernetes.io/cluster/CLUSTER_NAME (where CLUSTER_NAME is replaced with the name of the EKS Cluster) | list(string) |
n/a | yes |
suffix | Suffix added to the name. In case we need more then one profile in same namespace | string |
"" |
no |
tags | Additional tags (e.g. { Deployed = "xxxx" } |
map(string) |
{} |
no |
Name | Description |
---|---|
eks_fargate_profile_arn | Amazon Resource Name (ARN) of the EKS Fargate Profile |
eks_fargate_profile_id | EKS Cluster name and EKS Fargate Profile name separated by a colon |
eks_fargate_profile_role_arn | ARN of the EKS Fargate Profile IAM role |
eks_fargate_profile_role_name | Name of the EKS Fargate Profile IAM role |
eks_fargate_profile_status | Status of the EKS Fargate Profile |
$ make help
hooks Commit hooks setup
validate Validate with pre-commit hooks
changelog Update changelog
- π Use a succinct title and description.
- π Bugs & feature requests can be be opened
- πΆ Support questions are better asked on Stack Overflow
- π Be nice, civil and polite (as always).
Copyright 2019 ivankatliarhcuk
MIT Licensed. See LICENSE for full details.
Submit a pull request
Currently maintained by Ivan Katliarchuk and these awesome contributors.