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
@@ -17,7 +18,7 @@ The *Developer* perspective in the web console provides you the following option
17
18
** *Database*: Select the required database service and add it to your application.
18
19
** *Operator Backed*: Select and deploy the required Operator-managed service.
19
20
** *Helm chart*: Select the required Helm chart to simplify deployment of applications and services.
20
-
** *Event Source*: Select an Event source to register interest in a class of events from a particular system.
21
+
** *Event Source*: Select an event source to register interest in a class of events from a particular system.
21
22
+
22
23
[NOTE]
23
24
====
@@ -31,7 +32,7 @@ The Managed services option is also available if the RHOAS Operator is installed
31
32
* *Pipelines*: Use Tekton pipeline to create CI/CD pipelines for your software delivery process on the {product-title}.
32
33
33
34
* *Serverless*: Explore the *Serverless* options to create, build, and deploy stateless and serverless applications on the {product-title}.
34
-
** *Channel*: Create a Knative Channel to create an event forwarding and persistence layer with in-memory and reliable implementations.
35
+
** *Channel*: Create a Knative channel to create an event forwarding and persistence layer with in-memory and reliable implementations.
35
36
36
37
* *Samples*: Explore the available sample applications to create, build, and deploy an application quickly.
37
38
@@ -40,7 +41,7 @@ The Managed services option is also available if the RHOAS Operator is installed
40
41
** *Upload JAR file*: Upload a JAR file to build and deploy Java applications.
41
42
42
43
ifdef::openshift-enterprise,openshift-webscale[]
43
-
Note that certain options, such as *Pipelines*, *Event Source*, and *Import Virtual Machines*, are displayed only when the xref:../../cicd/pipelines/installing-pipelines.adoc#op-installing-pipelines-operator-in-web-console_installing-pipelines[OpenShift Pipelines Operator], xref:../../serverless/admin_guide/install-serverless-operator.adoc#serverless-install-web-console_install-serverless-operator[OpenShift Serverless Operator], and xref:../../virt/install/installing-virt-web.adoc#virt-subscribing-to-the-catalog_installing-virt-web[OpenShift Virtualization Operator] are installed, respectively.
44
+
Note that certain options, such as *Pipelines*, *Event Source*, and *Import Virtual Machines*, are displayed only when the xref:../../cicd/pipelines/installing-pipelines.adoc#op-installing-pipelines-operator-in-web-console_installing-pipelines[OpenShift Pipelines Operator], xref:../../serverless/admin_guide/install-serverless-operator.adoc#serverless-install-web-console_install-serverless-operator[{ServerlessOperatorName}], and xref:../../virt/install/installing-virt-web.adoc#virt-subscribing-to-the-catalog_installing-virt-web[OpenShift Virtualization Operator] are installed, respectively.
To create serverless applications, in addition to the preceding prerequisites, ensure that:
58
59
59
-
* You have xref:../../serverless/admin_guide/install-serverless-operator.adoc#install-serverless-operator[installed the OpenShift Serverless Operator].
60
+
* You have xref:../../serverless/admin_guide/install-serverless-operator.adoc#install-serverless-operator[installed the {ServerlessOperatorName}].
60
61
* You have xref:../../serverless/admin_guide/installing-knative-serving.adoc#installing-knative-serving[created a `KnativeServing` resource in the `knative-serving` namespace].
Copy file name to clipboardExpand all lines: modules/odc-importing-codebase-from-git-to-create-application.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Click the *Routing* link to:
55
55
* Select the target port for the traffic from the drop-down list.
56
56
* Secure your route by selecting the *Secure Route* check box. Select the required TLS termination type and set a policy for insecure traffic from the respective drop-down lists.
57
57
+
58
-
For serverless applications, the Knative Service manages all the routing options above. However, you can customize the target port for traffic, if required. If the target port is not specified, the default port of `8080` is used.
58
+
For serverless applications, the Knative service manages all the routing options above. However, you can customize the target port for traffic, if required. If the target port is not specified, the default port of `8080` is used.
59
59
60
60
Health Checks::
61
61
Click the *Health Checks* link to add Readiness, Liveness, and Startup probes to your application. All the probes have prepopulated default data; you can add the probes with the default data or customize it as required.
@@ -72,7 +72,7 @@ For each of the probes, you can specify the request type - *HTTP GET*, *Containe
72
72
Build Configuration and Deployment::
73
73
Click the *Build Configuration* and *Deployment* links to see the respective configuration options. Some options are selected by default; you can customize them further by adding the necessary triggers and environment variables.
74
74
+
75
-
For serverless applications, the *Deployment* option is not displayed as the Knative configuration resource maintains the desired state for your deployment instead of a DeploymentConfig.
75
+
For serverless applications, the *Deployment* option is not displayed as the Knative configuration resource maintains the desired state for your deployment instead of a `DeploymentConfig` resource.
76
76
77
77
Scaling::
78
78
Click the *Scaling* link to define the number of pods or instances of the application you want to deploy initially.
0 commit comments