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
feat: enable autoscaling on a given cluster (#138)
* feat: enable autoscaling on a given cluster
* fix: pre commit failures
* fix: add lifecycle to ignore addons
* fix: add validation for cluster_autoscaler_version
* fix: update the example
* fix: update examples
* fix: get addon list from user
* fix: remove autoscaling example and update logic
* docs: update docs
* fix: doc update
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ A module for provisioning an IBM Cloud Red Hat OpenShift cluster on VPC Gen2. Th
16
16
- Make sure that you have a recent version of the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started)
17
17
- Make sure that you have a recent version of the [IBM Cloud Kubernetes service CLI](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli)
18
18
19
-
20
-
21
19
## Usage
22
20
```hcl
23
21
# Replace "master" with a GIT release version to lock into a specific release
@@ -125,7 +123,7 @@ Optionally, you need the following permissions to attach Access Management tags
125
123
-[ Apply Taints Example](examples/apply_taints)
126
124
-[ Existing COS](examples/existing_cos)
127
125
-[ 2 MZR clusters in same VPC](examples/multiple_mzr_clusters)
128
-
-[ Single Zone Cluster](examples/single_zone_cluster)
126
+
-[ Single zone cluster example](examples/single_zone_cluster)
129
127
-[ Standard Example With User Managed Boot Volume Encryption](examples/standard)
130
128
<!-- END EXAMPLES HOOK -->
131
129
@@ -136,7 +134,9 @@ Optionally, you need the following permissions to attach Access Management tags
|[ibm_container_cluster_config.cluster_config](https://registry.terraform.io/providers/ibm-cloud/ibm/latest/docs/data-sources/container_cluster_config)| data source |
160
163
|[ibm_container_cluster_versions.cluster_versions](https://registry.terraform.io/providers/ibm-cloud/ibm/latest/docs/data-sources/container_cluster_versions)| data source |
161
164
@@ -164,6 +167,7 @@ Optionally, you need the following permissions to attach Access Management tags
164
167
| Name | Description | Type | Default | Required |
| <aname="input_access_tags"></a> [access\_tags](#input\_access\_tags)| A list of access tags to apply to the resources created by the module, see https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial for more details |`list(string)`|`[]`| no |
170
+
| <aname="input_addons"></a> [addons](#input\_addons)| List of all addons supported by the ocp cluster. | <pre>object({<br> alb-oauth-proxy = optional(string)<br> debug-tool = optional(string)<br> image-key-synchronizer = optional(string)<br> istio = optional(string)<br> openshift-data-foundation = optional(string)<br> static-route = optional(string)<br> cluster-autoscaler = optional(string)<br> vpc-block-csi-driver = optional(string)<br> })</pre> |`null`| no |
167
171
| <aname="input_cluster_name"></a> [cluster\_name](#input\_cluster\_name)| The name that will be assigned to the provisioned cluster |`string`| n/a | yes |
168
172
| <aname="input_cluster_ready_when"></a> [cluster\_ready\_when](#input\_cluster\_ready\_when)| The cluster is ready when one of the following: MasterNodeReady (not recommended), OneWorkerNodeReady, Normal, IngressReady |`string`|`"IngressReady"`| no |
169
173
| <aname="input_cos_name"></a> [cos\_name](#input\_cos\_name)| Name of the COS instance to provision. New instance only provisioned if `use_existing_cos = false`. Default: `<cluster_name>_cos`|`string`|`null`| no |
@@ -182,7 +186,7 @@ Optionally, you need the following permissions to attach Access Management tags
182
186
| <aname="input_verify_worker_network_readiness"></a> [verify\_worker\_network\_readiness](#input\_verify\_worker\_network\_readiness)| By setting this to true, a script will run kubectl commands to verify that all worker nodes can communicate successfully with the master. If the runtime does not have access to the kube cluster to run kubectl commands, this should be set to false. |`bool`|`true`| no |
183
187
| <aname="input_vpc_id"></a> [vpc\_id](#input\_vpc\_id)| Id of the VPC instance where this cluster will be provisioned |`string`| n/a | yes |
184
188
| <aname="input_vpc_subnets"></a> [vpc\_subnets](#input\_vpc\_subnets)| Metadata that describes the VPC's subnets. Obtain this information from the VPC where this cluster will be created | <pre>map(list(object({<br> id = string<br> zone = string<br> cidr_block = string<br> })))</pre> | n/a | yes |
pool_name ="default"# ibm_container_vpc_cluster automatically names default pool "default" (See https://github.com/IBM-Cloud/terraform-provider-ibm/issues/2849)
0 commit comments