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: platform/gcloud/README.md
+25-29Lines changed: 25 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -119,8 +119,8 @@ Regions and zones (used below) can be listed respectively with `gcloud compute r
119
119
```
120
120
121
121
> [!NOTE]
122
-
> You can also retrieve the command line to configure `kubectl` from the Google Cloud Console using the **Kubernetes Engine** > **Clusters** panel and clicking **Connect** on the dedicated cluster.
123
-
> 
122
+
> You can also retrieve the command line to configure `kubectl` from the Google Cloud Console using the **Kubernetes Engine** > **Clusters** panel and clicking **Connect** on the dedicated cluster.
123
+
> 
124
124
125
125
- Check your environment
126
126
@@ -138,36 +138,32 @@ We will use the Google Cloud Platform console to create the database instance.
138
138
139
139
- Go to the [SQL context](https://console.cloud.google.com/sql), and then click the **CREATE INSTANCE** button
140
140
- Click **Choose PostgreSQL**
141
+
- Database version: `PostgreSQL 15`
141
142
- Instance ID: ``<YourInstanceName>``
142
143
- Password: ``<PASSWORD>`` - Take note of this password.
143
-
- Database version: `PostgreSQL 15`
144
144
- Region: ``<REGION>`` (must be the same as the cluster for the communication to be optimal between the database and the ODM instance)
145
-
-Keep **Multiple zones** for Zonal availability to the highest availability
145
+
-Eventually select **Multiple zones** for Zonal availability for redundancy
146
146
- Expand **Show customization option** and expand **Connections**
147
147
- As *Public IP* is selected by default, in Authorized networks, click the **ADD NETWORK** button, put a name and add *0.0.0.0/0* for Network, then click **DONE**.
148
148
> NOTE: It is not recommended to use a public IP. In a production environment, you should use a private IP.
149
149
- Click **CREATE INSTANCE**
150
150
151
151
After the database instance is created, you can drill on the SQL instance overview to retrieve needed information to connect to this instance, like the IP address and the connection name. Take note of the **Public IP address**.
> NOTE: A default *postgres* database is created with a default *postgres* user. You can change the password of the postgres user in the **Users** panel by selecting the *postgres* user, and then using the **Change password** menu:
#### b. Create the database secret for Google Cloud SQL PostgreSQL
159
156
160
157
To secure access to the database, you must create a secret that encrypts the database user and password before you install the Helm release.
161
158
162
-
```
163
-
kubectl create secret generic <ODM_DB_SECRET> \
164
-
--from-literal=db-user=<USERNAME> \
165
-
--from-literal=db-password=<PASSWORD>
159
+
```shell
160
+
kubectl create secret generic odmdbsecret \
161
+
--from-literal=db-user=postgres \
162
+
--from-literal=db-password=<PASSWORD>
166
163
```
167
164
168
165
Where:
169
-
-`<ODM_DB_SECRET>` is the secret name
170
-
-`<USERNAME>` is the database username (default is *postgres*)
166
+
171
167
-`<PASSWORD>` is the database password (PASSWORD set during the PostgreSQL instance creation above)
172
168
173
169
### 3. Prepare your environment for the ODM installation (10 min)
@@ -180,39 +176,39 @@ To get access to the ODM material, you need an IBM entitlement key to pull the i
180
176
181
177
- In the Container software library tile, verify your entitlement on the **View library** page, and then go to **Get entitlement key** to retrieve the key.
182
178
183
-
#### b. Create a pull secret by running a kubectl create secret command.
179
+
#### b. Create a pull secret by running a kubectl create secret command
*`<API_KEY_GENERATED>` is the entitlement key from the previous step. Make sure you enclose the key in double-quotes.
197
-
*`<USER_EMAIL>` is the email address associated with your IBMid.
191
+
-`<API_KEY_GENERATED>` is the entitlement key from the previous step. Make sure you enclose the key in quotes.
192
+
-`<USER_EMAIL>` is the email address associated with your IBMid.
198
193
199
-
> NOTE: The `cp.icr.io` value for the docker-server parameter is the only registry domain name that contains the images. You must set the docker-username to `cp` to use an entitlement key as docker-password.
194
+
> [!NOTE]
195
+
> The `cp.icr.io` value for the docker-server parameter is the only registry domain name that contains the images. You must set the docker-username to `cp` to use an entitlement key as docker-password.
200
196
201
-
Take note of the secret name so that you can set it for the *image.pullSecrets* parameter when you run a helm install command of your containers. The *image.repository* parameter will later be set to `cp.icr.io/cp/cp4a/odm`.
197
+
The *image.repository* parameter will later be set to `cp.icr.io/cp/cp4a/odm`.
0 commit comments