batcave-tf-autoscaler

Requirements

Name	Version
terraform	>= 1.0
aws	>= 5.0.0
helm	~> 2.11.0
kubernetes	~> 2.23.0

Providers

Name	Version
aws	>= 5.0.0
helm	~> 2.11.0

Modules

Name	Source	Version
iam_assumable_role_admin	terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks	5.30.0

Resources

Name	Type
helm_release.autoscaler	resource
aws_eks_cluster_auth.cluster	data source

Inputs

Name	Description	Type	Default	Required
additional_values	Map of key/value pairs to pass to the autoscaler chart.	map(any)	{}	no
autoscaler_expander_method	Method by which CA will select a new instance to launch. Current options: random, most-pods, least-waste. See: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-expanders	string	"least-waste"	no
aws_region	n/a	string	"us-east-1"	no
cluster_certificate_authority_data	n/a	string	n/a	yes
cluster_endpoint	n/a	string	n/a	yes
cluster_name	n/a	string	n/a	yes
cluster_version	The version of the cluster. Used to determine the version of the autoscaler to deploy. Defaults to the most recent version known by this module.	string	""	no
cpu_limits	Pod limit values	string	"50m"	no
cpu_requests	n/a	string	"10m"	no
extraArgs	List of extraArgs values to pass to the autoscaler chart. See: https://github.com/kubernetes/autoscaler/blob/master/charts/cluster-autoscaler/values.yaml#L165	map(any)	{}	no
helm_namespace	## Helm variables	string	"kube-system"	no
iam_path	n/a	string	"/delegatedadmin/developer/"	no
memory_limits	n/a	string	"512Mi"	no
memory_requests	n/a	string	"50Mi"	no
monitoring_enabled	Enable monitoring for the cluster autoscaler; Note that this should not be enabled before bigbang is deployed, as it will fail to deploy since the monitoring namespace does not exist yet.	bool	false	no
oidc_provider_arn	n/a	string	""	no
permissions_boundary	n/a	string	"arn:aws:iam::373346310182:policy/cms-cloud-admin/developer-boundary-policy"	no

Outputs

Name	Description
oidc_iam_role_arn	n/a