Skip to content

Commit 8150ef1

Browse files
author
cfsdocs
committed
Build 2018
1 parent 9b5a3b2 commit 8150ef1

File tree

8 files changed

+46
-50
lines changed

8 files changed

+46
-50
lines changed

app-probes.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22

33
copyright:
4-
years: 2022, 2023
5-
lastupdated: "2023-12-12"
4+
years: 2022, 2024
5+
lastupdated: "2024-01-17"
66

77
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
88

@@ -116,8 +116,8 @@ Before you begin
116116
1. From the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}, go to your project.
117117
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.
118118
2. To view the configured probes and their properties for an app, go to the **Configuration** > **Image start options** tab on your application page.
119-
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.
120-
4. Click **Save and create** to save your change and deploy the app revision with the configured probe settings.
119+
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.
120+
4. Click **Deploy** to save your change and deploy the app revision with the configured probe settings.
121121

122122
Use the view on the **Instances** tab to check the application instances.
123123
{: tip}
@@ -277,9 +277,9 @@ You can modify or edit a readiness or liveness probe in the console, from the **
277277
* Click the name of your project to open the Overview page.
278278
* Click **Applications** to open a list of your applications. Click the name of your application to open its application page.
279279
2. From the application page, click the **Configuration** > **Image start options** tab on your application page.
280-
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.
280+
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.
281281
4. From the **Readiness probe** page or the **Liveness probe** page, update the [properties](#app-probes-properties) of your probe. Click **Done** when finished.
282-
5. Click **Save and create** to save your change and deploy the app revision.
282+
5. Click **Deploy** to save your change and deploy the app revision with the configured probe settings.
283283

284284
Use the view on the **Instances** tab to check the application instances.
285285
{: tip}
@@ -394,11 +394,10 @@ From the console, you can remove a liveness probe from the **Configuration** > *
394394
* Locate the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}.
395395
* Click the name of your project to open the Overview page.
396396
* Click **Applications** to open a list of your applications. Click the name of your application to open its application page.
397-
2. From the application page, click the **Configuration** > **Image start options** tab on your application page.
397+
2. From the application page, click the **Configuration** tab and then the **Image start options** tab on your application page.
398398
3. To remove a liveness probe, you must create a new application revision.
399-
1. Click **Edit and create new revision**.
400-
2. Click **Delete** to remove the liveness probe.
401-
3. Click **Save and create** to save your change and deploy the app revision.
399+
1. Click **Delete** to remove the liveness probe.
400+
2. Click **Deploy** to save your change and deploy the app revision.
402401
403402
While you cannot delete a readiness probe, you can [update](#app-probes-update-ui) it.
404403

app-scale.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2020, 2024
5-
lastupdated: "2024-01-11"
5+
lastupdated: "2024-01-17"
66

77
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
88

@@ -354,12 +354,11 @@ The default value for the maximum number of instances for your app is `0`, which
354354
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.
355355
356356
1. Navigate to your app.
357-
2. Select **Configuration**
358-
3. Click **Edit and create new revision**.
359-
4. Select **Runtime**.
357+
2. Select the **Configuration** tab.
358+
4. Select the **Resources & scaling** tab.
360359
5. Set the number for minimum and maximum instances for your app.
361360
6. (Optional) Review and set the request concurrency and timing settings for autoscaling your app.
362-
7. Click **Save and Create**.
361+
7. Click **Deploy** to save your changes and deploy the app revision.
363362
364363
When you update your application, your app creates a new revision and routes traffic to that instance.
365364

appdeploy-update.md

Lines changed: 16 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2020, 2024
5-
lastupdated: "2024-01-16"
5+
lastupdated: "2024-01-17"
66

77
keywords: 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, app, memory, cpu, environment variables
88

@@ -18,7 +18,7 @@ subcollection: codeengine
1818
An application contains one or more *revisions*. A revision represents an immutable version of the configuration properties of the application. Each update of an application configuration property creates a new revision of the application.
1919
{: shortdesc}
2020

21-
To create a revision, modify the application. If you are modifying your app, you must provide valid vCPU and memory combinations. For more information about these options, see [Options for deploying an app](/docs/codeengine?topic=codeengine-application-workloads#optionsdeploy)
21+
2222

2323

2424

@@ -56,11 +56,10 @@ Update the application that you created in [Deploying an application from a publ
5656
* Click the name of your project to open the Overview page.
5757
* Click **Applications** to open a list of your applications. Click the name of your application to open its application page.
5858
2. From the application page, you can view information about the running instances of your application and its revisions, configuration details, and endpoint settings of the app. Click the name of the application revision that you want to work with to open the configuration summary for that revision. Or, you can click the **Configuration** tab to open the configuration summary for the latest application revision.
59-
3. Click **Edit and create new revision** to change the app configuration.
60-
4. Click **Environment variables**.
61-
5. Click **Add environment variable**. Define this environment variable as a literal value. Enter `TARGET` for name and `Stranger` for value. Click **Done**.
62-
6. Click **Save and create** to save your change and deploy the application revision.
63-
7. After the application status changes to **Ready**, you can test the application revision. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**. For this app, `Hello Stranger` is displayed.
59+
3. From the **Configuration** tab, click the **Environment variables** tab.
60+
4. Click **Add environment variable**. Define this environment variable as a literal value. Enter `TARGET` for name and `Stranger` for value. Click **Add**.
61+
5. Click **Deploy** to save your change and deploy the application revision.
62+
6. After the application status changes to **Ready**, you can test the application revision. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**. For this app, `Hello Stranger` is displayed.
6463

6564
In this example, you updated environment variables for an app. You can also update other configuration settings for your app, including referencing a [different image](#update-app-crimage-console) or [different image build](#update-app-source-console) from the **Code** tab. From the **Resources & scaling** tab, you can update [memory](/docs/codeengine?topic=codeengine-mem-cpu-combo) and [application scaling](/docs/codeengine?topic=codeengine-app-scale) settings for your app. From the **Environment variables** tab, you can add or update [environment variables](/docs/codeengine?topic=codeengine-envvar) for your app. From the **Image start options** tab, you can add or update [command and arguments](/docs/codeengine?topic=codeengine-cmd-args) to override settings within your container image, or [work with liveness and readiness probes](/docs/codeengine?topic=codeengine-app-probes).
6665

@@ -483,17 +482,17 @@ For more information about adding an image to {{site.data.keyword.registryshort_
483482
* Locate the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}.
484483
* Click the name of your project to open the Overview page.
485484
* Click **Applications** to open a list of your applications. Click the name of your application to open the application page.
486-
2. Click **Configuration** to open the configuration details for the selected application revision.
487-
3. Click **Edit and create new revision** to update the application.
488-
4. From the **Code** tab, click **Configure image** to open the configure image dialog. For this example, update the app to reference an existing `ibmcregistry` registry, select the `mynamespace2` namespace, select the `helloworld-repo` image, and select `1` as the value for `tag`. From the configure image page,
485+
2. Click the **Configuration** tab to open the configuration details for the latest application revision.
486+
3. From the **Configuration** tab, click the **Code** tab.
487+
4. For Image to run, click **Configure image** to open the configure image dialog. For this example, update the app to reference an existing `ibmcregistry` registry, select the `mynamespace2` namespace, select the `helloworld-repo` image, and select `1` as the value for `tag`. From the configure image page,
489488
* If the image you want to use resides in the same {{site.data.keyword.registryshort_notm}} account, select the access for the registry.
490489
* If the image that you want to use resides in a different container registry account, you can select the registry access for this registry. If the registry access does not exist, you must first [create your IAM API key](/docs/codeengine?topic=codeengine-add-registry#images-your-account-api-key) and then [Add registry access to {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-add-registry#add-registry-access-ce).
491490
492491
If you want to update only the registry access to your image, you can make this change without clicking **Configure image** to open the configure image dialog and use the Registry access menu to select an existing registry access or [create a registry access to {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-add-registry#add-registry-access-ce) for the image that is referenced by your application.
493492
{: note}
494493
495494
5. Click **Done**. You selected your image in the registry to reference from your app.
496-
6. Click **Save and create** to save your change and deploy the app revision.
495+
6. Click **Deploy** to save your change and deploy the app revision.
497496
7. After the application status changes to **Ready**, you can test the app revision. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**. For this app, `Hello World from {{site.data.keyword.codeengineshort}}` is displayed.
498497
499498
### Updating an app to reference a different image in {{site.data.keyword.registryshort}} with the CLI
@@ -534,15 +533,14 @@ For more information about creating a build configuration from the console, see
534533
* Locate the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}.
535534
* Click the name of your project to open the Overview page.
536535
* Click **Applications** to open a list of your applications. Click the name of your application to open the application page.
537-
2. Click **Configuration** to open the configuration details for the selected application revision.
538-
3. Click **Edit and create new revision** to update the application.
536+
2. Click the **Configuration** tab to open the configuration details for the latest application revision.
537+
3. From the **Configuration** tab, click the **Code** tab.
539538
4. From the **Code** tab, you can create an image build, or you can rerun an existing image build that is referenced by your application. To create an image build, click **Create image from source** to run an image build. The Specify build details page opens where you can enter the details of your build to [deploy your app from source code](/docs/codeengine?topic=codeengine-app-source-code). Click **Done** when build detail updates are specified.
540-
5. Click **Save and create** to save your changes, run the build, and deploy the app revision.
539+
5. Click **Deploy** to save your changes, run the build, and deploy the app revision.
541540
6. After the application status changes to **Ready**, you can test the app revision. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**.
542-
7. To update this application again to reference an updated build image, click **Edit and create new revision** to update the application.
543-
8. From the **Code** tab, click **Rerun build** and specify a unique image tag for the updated build image. If you want to make more changes to the build details, click **Edit build details**. The Specify build details page opens where you can enter the details of your build to [deploy your app from source code](/docs/codeengine?topic=codeengine-app-source-code). Click **Done** when build detail updates are specified.
544-
9. Click **Save and create** to save your changes, run the build with your changes, and deploy the app revision.
545-
10. After the application status changes to **Ready**, you can test the app revision. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**.
541+
7. To update this application again to reference an updated build image, click **Rerun build** from the **Code** tab, and specify a unique image tag for the updated build image. If you want to make more changes to the build details, click **Edit build details**. The Specify build details page opens where you can enter the details of your build to [deploy your app from source code](/docs/codeengine?topic=codeengine-app-source-code). Click **Done** when build detail updates are specified.
542+
8. Click **Deploy** to save your changes, run the build with your changes, and deploy the app revision.
543+
9. After the application status changes to **Ready**, you can test the app revision. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**.
546544
547545
### Updating an app to reference an image that is built from source code with the CLI
548546
{: #update-app-source-cli}

batch-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2020, 2024
5-
lastupdated: "2024-01-09"
5+
lastupdated: "2024-01-17"
66

77
keywords: job tutorial, jobs, images for code engine jobs, tutorial for code engine, job log
88

@@ -103,8 +103,8 @@ When the job is in a ready state, you can update the job. Let's update the job t
103103
4. From the Submit job pane, review and optionally change default configuration values such as instances, CPU, memory, number of job retries, and job timeout. You can specify either **Array size** or **Array indices** for the parallel job instances to run. For **Array size**, provide the number of instances to run in parallel for this job. For **Array indices**, provide a comma-separated list for your custom set of indices. For example, to run this job with a custom set of `5` indices, specify `3,12-14,25`. Click **Submit job** again to run your job. The system displays the status of the instances of your job on the Job details page.
104104
5. By [viewing job logs from the console](/docs/codeengine?topic=codeengine-view-logs#view-joblogs-ui) for this job, the output of the job is `Hello World!`.
105105
6. To update the job again and add an environment variable, navigate to your job page.
106-
7. Click **Environment variables** to open the tab and then click **Add environment variable**. Add a literal environment variable with the name of `TARGET` with a value of `Sunshine`. The `icr.io/codeengine/testjob` outputs the message, `Hello <value_of_TARGET>!>`.
107-
8. Click **Done** to add your environment variable and then click **Save** to save the changes to your job.
106+
7. From the **Configuration > Enviroment variables** tab, click **Add environment variable**. Add a literal environment variable with the name of `TARGET` with a value of `Sunshine`. The `icr.io/codeengine/testjob` outputs the message, `Hello <value_of_TARGET>!>`.
107+
8. Click **Add** to add your environment variable and then click **Save** to save the changes to your job.
108108
9. Click **Submit job** to submit the updated job.
109109
10. From the Submit job pane, review and optionally change default configuration values such as instances, CPU, memory, number of job retries, and job timeout. This time, specify **Array size** as `3`. Click **Submit job** again to run your job. The system displays the status of the instances of your job on the Job details page. From the `Configuration` section of the Job details page, the information about the number of instances is displayed as **Array indices**, which is `0 - 2` for this example.
110110
11. By [viewing job logs from the console](/docs/codeengine?topic=codeengine-view-logs#view-joblogs-ui) for this job, the output of the updated job is `Hello Sunshine!`.

0 commit comments

Comments
 (0)