Terraform module for provisioning an EKS cluster
closes #123, if this PR closes a GitHub issue #123
go test dependencies to current to pick up bug and security fixes.Bumps sigs.k8s.io/aws-iam-authenticator from 0.5.3 to 0.5.9.
Sourced from sigs.k8s.io/aws-iam-authenticator's releases.
v0.5.9
Changelog
- 1209cfe2 Bump version in Makefile
- 029d1dcf Add query parameter validation for multiple parameters
v0.5.7
What's Changed
- Remove duplicate InitMetrics by
@jngo2in kubernetes-sigs/aws-iam-authenticator#448
- fixes a crash when executing authenticator in server mode
New Contributors
@jngo2made their first contribution in kubernetes-sigs/aws-iam-authenticator#448Full Changelog: https://github.com/kubernetes-sigs/aws-iam-authenticator/compare/v0.5.6...v0.5.7
v0.5.6
Changelog
- Bump AWS SDK to v1.43.28 (#445,
@nckturner)- Use the apiversion from KUBERNETES_EXEC_INFO (#439,
@jyotimahapatra)- Bump promptui module to v0.9.0 (#437,
@abhay-krishna)Docker Images
Note: You must log in with the registry ID and your role must have the necessary ECR privileges:
$(aws ecr get-login --no-include-email --region us-west-2 --registry-ids 602401143452)
docker pull 602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-iam-authenticator:v0.5.6docker pull 602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-iam-authenticator:v0.5.6-arm64docker pull 602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-iam-authenticator:v0.5.6-amd64v0.5.5
Changelog
- Use full package name for goreleaser version (#433,
@nckturner)- add sts error metric (#430,
@jyotimahapatra)- emit metric for EC2 describeInstance calls (#428,
@jyotimahapatra)- Rename configmap_watch_failures to configmap_watch_failures_total (#432,
@nckturner)- Simplify goreleaser Dockerfiles (#431,
@jyotimahapatra)- Don't pass metrics around (#423,
@nckturner)Docker Images
Note: You must log in with the registry ID and your role must have the necessary ECR privileges:
$(aws ecr get-login --no-include-email --region us-west-2 --registry-ids 602401143452)
... (truncated)
1209cfe Bump version in Makefile029d1dc Add query parameter validation for multiple parameters0a72c12 Merge pull request #455 from jyotimahapatra/rev2596a043 revert use of upstream yaml parsing2a9ee95 Merge pull request #448 from jngo2/masterfc4e6cb Remove unused importsf0fe605 Remove duplicate InitMetrics99f04d6 Merge pull request #447 from nckturner/release-0.5.69dcb6d1 Faster multiarch docker buildsa9cc81b Bump timeout for image build jobhashicorp/tls provider version >= 4.0.0When using hashicorp/tls provider v4.0.0 and setting oidc_provider_enabled = true on a new EKS cluster deployment, terraform plan will fail with thumbprint_list = [join("", data.tls_certificate.cluster.*.certficates.0.sha1_fingerprint)] and The given key does not identify an element in this collection value: the collection has no elements.
This release is identical to version 0.45.0 and is just a renumbering to provide production-level semantic versioning. No migration is needed from v0.45.0 or later.
Version 2.0 includes updates to use our new security group module, which is a breaking change. See the V1 to V2 migration documentation for details on how to safely migrate.
This 1.0.0 release is identical to v0.44.0 and is simply a conversion to production Semantic Versioning. If you are already using a later pre-1.0 version, do not migrate to this version, migrate directly to v2.0.0 or later/
This is the first (oldest code) release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules, especially those where we see breaking changes coming in the near future. This module already has a Version 2.0 with breaking changes.
PR #150
wait_for_cluster_command, supersedes #145, closes #146git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.This module creates an EKS cluster, which automatically creates an EKS-managed Security Group in which all managed nodes are placed automatically by EKS, and unmanaged nodes could be placed by the user, to ensure the nodes and control plane can communicate.
Before version 0.45.0, this module, by default, created an additional Security Group. Prior to version 0.19.0 of this module, that additional Security Group was the only one exposed by
this module (because EKS at the time did not create the managed Security Group for the cluster), and it was intended that all worker nodes (managed and unmanaged) be placed in this
additional Security Group. With version 0.19.0, this module exposed the managed Security Group created by the EKS cluster, in which all managed node groups are placed by default. We now
recommend placing non-managed node groups in the EKS-created Security Group as well by using the allowed_security_group_ids variable, and not create an additional Security Group.