Merge pull request #482 from cloud-docs/next-publish-push

Next publish push

Author: foverby

add-registry.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-11"
+lastupdated: "2024-01-22"
 
 keywords: registries, container registry, image registry, apikey, API key, access token, images, registry access, registry secret, service id,registry secret, registry access secret
 
@@ -184,22 +184,27 @@ To set up access to an {{site.data.keyword.registryfull_notm}} in a different {{
 ### Adding registry access from the console
 {: #add-registry-access-ce-console}
 
-To add {{site.data.keyword.registryfull_notm}} or Docker Hub access with the console,
+Before you begin, [create a project](/docs/codeengine?topic=codeengine-manage-project).
 
-1. Go to the [{{site.data.keyword.codeengineshort}} dashboard](https://cloud.ibm.com/codeengine/overview).
-2. Select a project (or [create one](/docs/codeengine?topic=codeengine-manage-project#create-a-project)).
-3. From the project page, click **Registry access**.
-4. Click **Create**.
-5. Select **Docker Hub** or **Custom**.
-6. Enter a name for your registry access.
-7. Enter a server name for your registry. For {{site.data.keyword.registryshort}}, the server name is `<region>.icr.io`. For example, `us.icr.io`. For [Docker Hub](https://hub.docker.com/), the server name is `https://index.docker.io/v1/`.
-8. Enter a username. For {{site.data.keyword.registryfull_notm}}, it is `iamapikey`. For Docker Hub, it is your Docker ID.
-9. Enter the password. For {{site.data.keyword.registryfull_notm}}, the password is your API key. For Docker Hub, you can use your Docker Hub password or an [access token](#access-private-docker-hub).
-10. Click **Create**.
+1. After your project is in **Active** status, click the name of your project on the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}. 
+2. From the Components page, click **Secrets and configmaps**.
+3. From the Secrets and configmaps page, click **Create** to create your secret.
+4. From the Create secret or configmap page, complete the following steps:
+    1. Select **Registry secret**, and click **Next**.
+    2. Provide a name; for example, `mysecret-registry`.
+    3. Specify the target registry for this secret, such as {{site.data.keyword.registrylong_notm}} or Docker Hub.
+    4. Specify the location of the registry. 
+    5. Specify a username. If this secret is for {{site.data.keyword.registrylong_notm}}, the username is `iamapikey`. If this secret is for Docker Hub, it is your Docker ID.
+    6. Enter the credentials for the username. For {{site.data.keyword.registryfull_notm}}, use your IAM API key. For Docker Hub, you can use your Docker Hub password or an [access token](#access-private-docker-hub). For other target registries, specify the password or API key for the username.
+    7. Click **Create** to create the secret. 
 
-You can add access to a container registry when you create an application or job, or when you build an image. Click **Configure image** and specify the container image to run, including the registry where the image is stored and the [registry access](/docs/codeengine?topic=codeengine-add-registry#types-registryaccesssecrets) to use to retrieve the image.  Follow previous steps 5-9.
+Now that your secret is created from the console, go to the Secrets and configmaps page to view a list of defined secrets and configmaps. You can apply filters to customize the list to meet your needs. 
+
+You can add access to a container registry when you create an application or job, or when you build an image. Click **Configure image** and specify the container image to run, including the registry where the image is stored and the [registry access](/docs/codeengine?topic=codeengine-add-registry#types-registryaccesssecrets) to use to retrieve the image. 
 {: tip}
 
+
+
 ### Adding registry access with the CLI
 {: #add-registry-access-ce-cli}
 

app-probes.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2022, 2023
-lastupdated: "2023-12-12"
+  years: 2022, 2024
+lastupdated: "2024-01-17"
 
 keywords: domain mapping, custom domain, applications in code engine, apps in code engine, http requests in code engine, deploy apps in code engine, app workloads in code engine, deploying workloads in code engine, application, domain mappings, custom domain mappings, CNAME, TLS, TLS secret, private key, certificate
 
@@ -116,8 +116,8 @@ Before you begin
 1. From the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}, go to your project.
 2. [Create an application](/docs/codeengine?topic=codeengine-cli#cli-application-create). For example, create an application that is called `myapp` that uses the `icr.io/codeengine/helloworld` image. This image is available from the [Samples for {{site.data.keyword.codeenginefull_notm}} GitHub repo](https://github.com/IBM/CodeEngine/tree/main/cron){: external}. You can configure liveness and readiness probes when you create an application. Or, you can view and update settings for liveness and readiness probes when you update an application from the **Configuration** > **Image start options** tab on your application page. 
 2. To view the configured probes and their properties for an app, go to the **Configuration** > **Image start options** tab on your application page. 
-3. To modify or edit a readiness or liveness probe, click **Edit and create new revision**. Modifying a probe creates a new application revision. For example, edit the default readiness probe to change the connection type from TCP to HTTP, and set the path for the readiness probe to `/readinessprobe`. See [properties](#app-probes-properties) for more information about the probe properties. Click **Done** when finished. 
-4. Click **Save and create** to save your change and deploy the app revision with the configured probe settings.
+3. Edit the liveness and readiness probe settings from the **Image start options** tab. Modifying a probe creates a new application revision. For example, edit the default readiness probe to change the connection type from TCP to HTTP, and set the path for the readiness probe to `/readinessprobe`. See [properties](#app-probes-properties) for more information about the probe properties. Click **Done** when finished. 
+4. Click **Deploy** to save your change and deploy the app revision with the configured probe settings.
 
 Use the view on the **Instances** tab to check the application instances. 
 {: tip}
@@ -277,9 +277,9 @@ You can modify or edit a readiness or liveness probe in the console, from the **
     * Click the name of your project to open the Overview page.
     * Click **Applications** to open a list of your applications. Click the name of your application to open its application page.
 2. From the application page, click the  **Configuration** > **Image start options** tab on your application page. 
-3. To modify or edit a readiness or liveness probe, you must create a new application revision. Click **Edit and create new revision**. Click **Edit** to modify the readiness or liveness probe that you want to change. 
+3. Edit the liveness and readiness probe settings from the **Image start options** tab. Modifying a probe creates a new application revision. Click **Edit** to modify the readiness or liveness probe that you want to change. 
 4. From the **Readiness probe** page or the **Liveness probe** page, update the [properties](#app-probes-properties) of your probe. Click **Done** when finished. 
-5. Click **Save and create** to save your change and deploy the app revision.
+5. Click **Deploy** to save your change and deploy the app revision with the configured probe settings.
 
 Use the view on the **Instances** tab to check the application instances. 
 {: tip}
@@ -394,11 +394,10 @@ From the console, you can remove a liveness probe from the **Configuration** > *
     * Locate the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}. 
     * Click the name of your project to open the Overview page.
     * Click **Applications** to open a list of your applications. Click the name of your application to open its application page.
-2. From the application page, click the  **Configuration** > **Image start options** tab on your application page. 
+2. From the application page, click the  **Configuration** tab and then the **Image start options** tab on your application page. 
 3. To remove a liveness probe, you must create a new application revision. 
-    1. Click **Edit and create new revision**. 
-    2. Click **Delete** to remove the liveness probe. 
-    3. Click **Save and create** to save your change and deploy the app revision.
+    1. Click **Delete** to remove the liveness probe. 
+    2. Click **Deploy** to save your change and deploy the app revision.
 
 While you cannot delete a readiness probe, you can [update](#app-probes-update-ui) it. 
 

app-scale.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-11"
+lastupdated: "2024-01-17"
 
 keywords: application scaling in code engine, scaling http requests in code engine, concurrency in code engine applications, latency in code engine applications, throughput in code engine applications, scaling, latency, concurrency, app
 
@@ -354,12 +354,11 @@ The default value for the maximum number of instances for your app is `0`, which
 To change the range within which {{site.data.keyword.codeengineshort}} autoscales the number of running instances for an app from the console, follow these steps.
 
 1. Navigate to your app.
-2. Select **Configuration**
-3. Click **Edit and create new revision**.
-4. Select **Runtime**.
+2. Select the **Configuration** tab.
+4. Select the **Resources & scaling** tab.
 5. Set the number for minimum and maximum instances for your app.
 6. (Optional) Review and set the request concurrency and timing settings for autoscaling your app. 
-7. Click **Save and Create**.
+7. Click **Deploy** to save your changes and deploy the app revision.
 
 When you update your application, your app creates a new revision and routes traffic to that instance.