Releases: cloudposse/terraform-aws-components
Releases · cloudposse/terraform-aws-components
v1.458.0
fix(DEV-2294): Docusarus Rendering @milldr (#1060)
what
- Removed or fixed broken links on docs website
- Remove pipe character from descriptions
|
why
- We cant use relative links for links since the READMEs and CHANGELOGs are copied and formatted for Docusarus
- The pipe character
|
in a description breaks table rendering
references
[WARNING] Docs markdown link couldn't be resolved: (./README.md) in "...components/library/aws/eks/cluster/cluster.md" for version current
[WARNING] Docs markdown link couldn't be resolved: (./docs/v1alpha-to-v1beta-migration.md) in "...components/library/aws/eks/karpenter/karpenter.md" for version current
SyntaxError: ...components/library/aws/eks/karpenter-node-pool/karpenter-node-pool.md: Expected corresponding JSX closing tag for <pre>. (464:1394)
462 | <td parentName="tr" {...{"align":null}}><a name="input_node_pools"></a>{` `}<a parentName="td" {...{"href":"#input_node_pools"}}>{`node`}{`_`}{`pools`}</a></td>
463 | <td parentName="tr" {...{"align":null}}>{`Configuration for node pools. See code for details.`}</td>
> 464 | <td parentName="tr" {...{"align":null}}><pre>{`map(object({`}<br/>{` # The name of the Karpenter provisioner. The map key is used if this is not set.`}<br/>{` name = optional(string)`}<br/>{` # Whether to place EC2 instances launched by Karpenter into VPC private subnets. Set it to 'false' to use public subnets.`}<br/>{` private_subnets_enabled = bool`}<br/>{` # The Disruption spec controls how Karpenter scales down the node group.`}<br/>{` # See the example (sadly not the specific 'spec.disruption' documentation) at `}<a parentName="td" {...{"href":"https://karpenter.sh/docs/concepts/nodepools/"}}>{`https://karpenter.sh/docs/concepts/nodepools/`}</a>{` for details`}<br/>{` disruption = optional(object({`}<br/>{` # Describes which types of Nodes Karpenter should consider for consolidation.`}<br/>{` # If using 'WhenUnderutilized', Karpenter will consider all nodes for consolidation and attempt to remove or`}<br/>{` # replace Nodes when it discovers that the Node is underutilized and could be changed to reduce cost.`}<br/>{` # If using 'WhenEmpty', Karpenter will only consider nodes for consolidation that contain no workload pods.`}<br/>{` consolidation_policy = optional(string, "WhenUnderutilized")`}<br/><br/>{` # The amount of time Karpenter should wait after discovering a consolidation decision ('go' duration string, s`}</td>
| ^
465 | <td parentName="tr" {...{"align":null}}>{`m`}</td>
466 | <td parentName="tr" {...{"align":"center"}}>{`h).`}<br/>{` # This value can currently (v0.36.0) only be set when the consolidationPolicy is 'WhenEmpty'.`}<br/>{` # You can choose to disable consolidation entirely by setting the string value 'Never' here.`}<br/>{` # Earlier versions of Karpenter called this field 'ttl_seconds_after_empty'.`}<br/>{` consolidate_after = optional(string)`}<br/><br/>{` # The amount of time a Node can live on the cluster before being removed ('go' duration string, s`}</td>
467 | </tr>
v1.457.0
v1.456.0
v1.455.1
v1.455.0
fix: allow component to deploy correctly when create_namespace is false @agfunderburg10 (#1011)
Correct description and doc to match actual default value of create_namespace var
what
- changes value of
kubernetes_namespace
to consider thecreate_namespace
variable value - corrects doc and description to show default
create_namespace
value astrue
why
The kubernetes_namespace
value that is passed into the "cloudposse/helm-release/aws" module was set as join("", kubernetes_namespace.default.*.id)
. When create_namespace
is false
, this resource is never created, resulting in an error (example below) during deployment. My fix will simply use the variable kubernetes_namespace
if create_namespace
is false.
Error example:
module.metrics_server.helm_release.this[0]: Creating...
╷
│ Error: create: failed to create: an empty namespace may not be set during creation
│
│ with module.metrics_server.helm_release.this[0],
│ on .terraform/modules/metrics_server/main.tf line 65, in resource "helm_release" "this":
│ 65: resource "helm_release" "this" {
│
╵
exit status 1
v1.454.0
[eks/actions-runner-controller] Add ability to dynamically annotate pods once they start a job @Nuru (#1055)
what
For eks/actions-runner-controller
- Add ability to dynamically annotate pods once they start a job
- Add ability to specify runner pod affinities and anti-affinities
- Deprecate
storage
in favor ofdocker_storage
to configure how much disk space to allocate for the Docker daemon - Miscellaneous cleanups of inputs and chart
why
- Allow idle runners to be evicted by Karpenter for purposes of node consolidation, while preventing running runners from being interrupted
- Allow runners to have more control over where they are placed
- The term "storage" is too vague, and could reasonably be expected to configure the worker storage, but in fact it only configures the Docker storage. (Storage size for the optional PVC is still hardcoded at 100Gi.)
- Make chart a bit more readable and maintainable
references
v1.453.0
v1.452.0
[eks/cluster] Add support for kubelet extra args, etc. @Nuru (#1046)
what
- [
eks/cluster
] Add support forkubelet
extra args and other Node cloud-init customizations for EKS running on Amazon Linux 2
why
- Default values of reserved memory are insufficient to keep EKS nodes from becoming unreachable due to excessive demands from Pods, so this provides a way for changing the reservations and enabling eviction thresholds
v1.451.0
v1.450.0
- No changes