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
Copy file name to clipboardExpand all lines: solutions/standard-openshift/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,10 +73,10 @@ This example sets up an OpenShift Cluster on PowerVS following infrastructure:
73
73
| <aname="input_ansible_vault_password"></a> [ansible\_vault\_password](#input\_ansible\_vault\_password)| Vault password to encrypt ansible playbooks that contain sensitive information. Password requirements: 15-100 characters and at least one uppercase letter, one lowercase letter, one number, and one special character. Allowed characters: A-Z, a-z, 0-9, !#$%&()*+-.:;<=>?@[]\_{\|}~. |`string`| n/a | yes |
74
74
| <aname="input_client_to_site_vpn"></a> [client\_to\_site\_vpn](#input\_client\_to\_site\_vpn)| VPN configuration - the client ip pool and list of users email ids to access the environment. If enabled, then a Secret Manager instance is also provisioned with certificates generated. See optional parameters to reuse an existing Secrets manager instance. | <pre>object({<br/> enable = bool<br/> client_ip_pool = string<br/> vpn_client_access_group_users = list(string)<br/> })</pre> | <pre>{<br/> "client_ip_pool": "192.168.0.0/16",<br/> "enable": true,<br/> "vpn_client_access_group_users": []<br/>}</pre> | no |
75
75
| <aname="input_cluster_base_domain"></a> [cluster\_base\_domain](#input\_cluster\_base\_domain)| The base domain name that will be used by the cluster. Only .test, .example, and .invalid domains are supported (ie: domain.example). |`string`| n/a | yes |
76
-
| <aname="input_cluster_master_node_config"></a> [cluster\_master\_node\_config](#input\_cluster\_master\_node\_config)| Configuration for the master nodes of the OpenShift cluster, including CPU, system type, processor type, and replica count. If system\_type is null, it's chosen based on whether it's supported in the region. This can be overwritten by passing a value, e.g. 's1022' or 's922'. Memory is in GB. | <pre>object({<br/> processors = number<br/> memory = number<br/> system_type = string<br/> proc_type = string<br/> replicas = number<br/> })</pre> | <pre>{<br/> "memory": 32,<br/> "proc_type": "Shared",<br/> "processors": 4,<br/> "replicas": 3,<br/> "system_type": null<br/>}</pre> | no |
76
+
| <aname="input_cluster_master_node_config"></a> [cluster\_master\_node\_config](#input\_cluster\_master\_node\_config)| Configuration for the master nodes of the OpenShift cluster, including CPU, system type, processor type, and replica count. If system\_type is null, it's chosen based on whether it's supported in the region. This can be overwritten by passing a value, e.g. 's1022' or 's922'. Memory is in GB. | <pre>object({<br/> processors = number<br/> memory = number<br/> system_type = string<br/> proc_type = string<br/> replicas = number<br/> })</pre> | <pre>{<br/> "memory": "32",<br/> "proc_type": "Shared",<br/> "processors": "4",<br/> "replicas": "3",<br/> "system_type": "null"<br/>}</pre> | no |
77
77
| <aname="input_cluster_name"></a> [cluster\_name](#input\_cluster\_name)| The name of the cluster and a unique identifier used as prefix for resources. Must begin with a lowercase letter and end with a lowercase letter or number. Must contain only lowercase letters, numbers, and - characters. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 16 or fewer characters. |`string`| n/a | yes |
78
78
| <aname="input_cluster_network_config"></a> [cluster\_network\_config](#input\_cluster\_network\_config)| Configuration object for the OpenShift cluster and service network CIDRs. | <pre>object({<br/> cluster_network_cidr = string<br/> cluster_service_network_cidr = string<br/> cluster_machine_network_cidr = string<br/> })</pre> | <pre>{<br/> "cluster_machine_network_cidr": "10.72.0.0/24",<br/> "cluster_network_cidr": "10.128.0.0/14",<br/> "cluster_service_network_cidr": "10.67.0.0/16"<br/>}</pre> | no |
79
-
| <aname="input_cluster_worker_node_config"></a> [cluster\_worker\_node\_config](#input\_cluster\_worker\_node\_config)| Configuration for the worker nodes of the OpenShift cluster, including CPU, system type, processor type, and replica count. If system\_type is null, it's chosen based on whether it's supported in the region. This can be overwritten by passing a value, e.g. 's1022' or 's922'. Memory is in GB. | <pre>object({<br/> processors = number<br/> memory = number<br/> system_type = string<br/> proc_type = string<br/> replicas = number<br/> })</pre> | <pre>{<br/> "memory": 32,<br/> "proc_type": "Shared",<br/> "processors": 4,<br/> "replicas": 3,<br/> "system_type": null<br/>}</pre> | no |
79
+
| <aname="input_cluster_worker_node_config"></a> [cluster\_worker\_node\_config](#input\_cluster\_worker\_node\_config)| Configuration for the worker nodes of the OpenShift cluster, including CPU, system type, processor type, and replica count. If system\_type is null, it's chosen based on whether it's supported in the region. This can be overwritten by passing a value, e.g. 's1022' or 's922'. Memory is in GB. | <pre>object({<br/> processors = number<br/> memory = number<br/> system_type = string<br/> proc_type = string<br/> replicas = number<br/> })</pre> | <pre>{<br/> "memory": "32",<br/> "proc_type": "Shared",<br/> "processors": "4",<br/> "replicas": "3",<br/> "system_type": "null"<br/>}</pre> | no |
80
80
| <aname="input_enable_monitoring"></a> [enable\_monitoring](#input\_enable\_monitoring)| Specify whether Monitoring will be enabled. This includes the creation of an IBM Cloud Monitoring Instance and an Intel Monitoring Instance to host the services. If you already have an existing monitoring instance then specify in optional parameter 'existing\_monitoring\_instance\_crn' and setting this parameter to true. |`bool`|`false`| no |
81
81
| <aname="input_enable_scc_wp"></a> [enable\_scc\_wp](#input\_enable\_scc\_wp)| Enable SCC Workload Protection and install and configure the SCC Workload Protection agent on all intel VSIs in this deployment. |`bool`|`true`| no |
82
82
| <aname="input_existing_monitoring_instance_crn"></a> [existing\_monitoring\_instance\_crn](#input\_existing\_monitoring\_instance\_crn)| Existing CRN of IBM Cloud Monitoring Instance. If value is null, then an IBM Cloud Monitoring Instance will not be created but an intel VSI instance will be created if 'enable\_monitoring' is true. |`string`|`null`| no |
@@ -86,7 +86,7 @@ This example sets up an OpenShift Cluster on PowerVS following infrastructure:
86
86
| <aname="input_ibmcloud_api_key"></a> [ibmcloud\_api\_key](#input\_ibmcloud\_api\_key)| The IBM Cloud platform API key needed to deploy IAM enabled resources. |`string`| n/a | yes |
87
87
| <aname="input_intel_user_data"></a> [intel\_user\_data](#input\_intel\_user\_data)| User data that automatically performs common configuration tasks or runs scripts only on the intel VSIs. For more information, see https://cloud.ibm.com/docs/vpc?topic=vpc-user-data. For information on using the user\_data variable, please refer: https://cloud.ibm.com/docs/secure-infrastructure-vpc?topic=secure-infrastructure-vpc-user-data|`string`|`null`| no |
88
88
| <aname="input_network_services_vsi_profile"></a> [network\_services\_vsi\_profile](#input\_network\_services\_vsi\_profile)| Compute profile configuration of the network services vsi (cpu and memory configuration). Must be one of the supported profiles. See [here](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=ui). |`string`|`"cx2-2x4"`| no |
89
-
| <aname="input_openshift_pull_secret"></a> [openshift\_pull\_secret](#input\_openshift\_pull\_secret)| Pull secret from Red Hat OpenShift Cluster Manager for authenticating OpenShift image downloads from Red Hat container registries. A RedHat account is required. It can be obtained on https://console.redhat.com/openshift/install/pull-secret.|`map(any)`| n/a | yes |
89
+
| <aname="input_openshift_pull_secret"></a> [openshift\_pull\_secret](#input\_openshift\_pull\_secret)| Pull secret from Red Hat OpenShift Cluster Manager for authenticating OpenShift image downloads from Red Hat container registries. A RedHat account is required. It can be obtained on https://console.redhat.com/openshift/install/pull-secret.|`string`| n/a | yes |
90
90
| <aname="input_openshift_release"></a> [openshift\_release](#input\_openshift\_release)| The OpenShift IPI release version to deploy. |`string`|`"4.19.13"`| no |
91
91
| <aname="input_powervs_zone"></a> [powervs\_zone](#input\_powervs\_zone)| IBM Cloud data center location where IBM PowerVS infrastructure will be created. Supported regions are: dal10, dal12, eu-de-1, eu-de-2, lon04, lon06, mad02, mad04, osa21, sao01, sao04, syd04, syd05, us-east, us-south, wdc06, wdc07. |`string`| n/a | yes |
92
92
| <aname="input_sm_service_plan"></a> [sm\_service\_plan](#input\_sm\_service\_plan)| The service/pricing plan to use when provisioning a new Secrets Manager instance. Allowed values: `standard` and `trial`. Only used if `existing_sm_instance_guid` is set to null. |`string`|`"standard"`| no |
Copy file name to clipboardExpand all lines: solutions/standard-openshift/variables.tf
+15-15Lines changed: 15 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ variable "user_id" {
30
30
31
31
variable"openshift_pull_secret" {
32
32
description="Pull secret from Red Hat OpenShift Cluster Manager for authenticating OpenShift image downloads from Red Hat container registries. A RedHat account is required. It can be obtained on https://console.redhat.com/openshift/install/pull-secret."
0 commit comments