diff --git a/applications/application-life-cycle-management/odc-creating-applications-using-developer-perspective.adoc b/applications/application-life-cycle-management/odc-creating-applications-using-developer-perspective.adoc index fd102f32e0..0095acf1aa 100644 --- a/applications/application-life-cycle-management/odc-creating-applications-using-developer-perspective.adoc +++ b/applications/application-life-cycle-management/odc-creating-applications-using-developer-perspective.adoc @@ -16,10 +16,12 @@ image::odc_add_view.png[Add View] * *YAML*: Use the editor to add YAML or JSON definitions to create and modify resources. * *Database*: See the *Developer Catalog* to select the required database service and add it to your application. +ifdef::openshift-enterprise,openshift-origin[] [NOTE] ==== The serverless sections in the above options are displayed only if the xref:../../serverless/installing-openshift-serverless.adoc#installing-openshift-serverless[*Serverless Operator*] is installed in your cluster. OpenShift Serverless is a Technology Preview feature. ==== +endif::[] .Prerequisites To create applications using the *Developer* perspective ensure that: @@ -28,9 +30,13 @@ To create applications using the *Developer* perspective ensure that: * You are in the xref:../../web-console/odc-about-developer-perspective.adoc#odc-about-developer-perspective[*Developer* perspective]. * You have the appropriate xref:../../authentication/using-rbac.adoc#default-roles_using-rbac[roles and permissions] in a project to create applications and other workloads in {product-title}. +ifdef::openshift-enterprise,openshift-origin[] + To create serverless applications, in addition to the above, ensure that: * You have xref:../../serverless/installing-openshift-serverless.adoc#installing-serverless-operator_installing-openshift-serverless[installed the Openshift Serverless Operator]. * You have xref:../../serverless/installing-openshift-serverless.adoc#installing-knative-serving_installing-openshift-serverless[created a knative-serving namespace and a KnativeServing resource in the knative-serving namespace]. +endif::[] + include::modules/odc-importing-codebase-from-git-to-create-application.adoc[leveloffset=+1] diff --git a/openshift_images/images-understand.adoc b/openshift_images/images-understand.adoc index d8025934ac..d05fd3b4f6 100644 --- a/openshift_images/images-understand.adoc +++ b/openshift_images/images-understand.adoc @@ -30,6 +30,8 @@ include::modules/images-imagestream-trigger.adoc[leveloffset=+1] == Additional resources +ifdef::openshift-enterprise,openshift-origin[] * For more information on using imagestreams, see xref:../openshift_images/image-streams-manage.adoc#managing-image-streams[Managing image streams]. +endif::[] diff --git a/welcome/index.adoc b/welcome/index.adoc index 978201a7e0..30c90edd22 100644 --- a/welcome/index.adoc +++ b/welcome/index.adoc @@ -103,11 +103,13 @@ The odo CLI tool lets developers create single or multi-component applications easily and automates deployment, build, and service route configurations. It abstracts complex Kubernetes and {product-title} concepts, allowing developers to focus on developing their applications. +ifdef::openshift-enterprise,openshift-origin[] - **Deploy Helm Charts**: xref:../cli_reference/helm-cli/getting-started-with-helm-on-openshift-container-platform.adoc#getting-started-with-helm-on-openshift[Helm 3] is a package manager that helps developers define, install, and update application packages on Kubernetes. A Helm Chart is a packaging format that describes an application that can be deployed using the Helm CLI. +endif::[] - **xref:../operators/olm-what-operators-are.adoc#olm-what-operators-are[Understand Operators]**: Operators are the preferred method for creating on-cluster applications for {product-title} {product-version}. Learn about the Operator Framework and how to deploy applications using installed Operators into your projects. @@ -201,7 +203,9 @@ be reviewed by cluster administrators and xref:../operators/olm-adding-operators - **xref:../operators/crds/crd-extending-api-with-crds.adoc#crd-extending-api-with-crds[Use Custom Resource Definition (CRDs) to modify the cluster]**: Cluster features that are implemented with Operators, can be modified with CRDs. Learn to xref:../operators/crds/crd-extending-api-with-crds.adoc#crd-creating-custom-resources-definition_crd-extending-api-with-crds[create a CRD] and xref:../operators/crds/crd-managing-resources-from-crds.adoc#crd-managing-resources-from-crds[manage resources from CRDs]. +ifdef::openshift-enterprise,openshift-origin[] - **xref:../applications/quotas/quotas-setting-per-project.adoc#quotas-setting-per-project[Set resource quotas]**: Choose from CPU, memory and other system resources to xref:../applications/quotas/quotas-setting-per-project.adoc#quotas-setting-per-project[set quotas]. +endif::[] - **xref:../applications/pruning-objects.adoc#pruning-objects[Prune and reclaim resources]**: You can reclaim space by pruning unneeded Operators, groups, deployments, builds, images, registries, and cron jobs. @@ -245,8 +249,12 @@ be reviewed by cluster administrators and xref:../operators/olm-adding-operators - **xref:../administering_a_cluster/dedicated-admin-role.adoc#dedicated-managing-administrators_dedicated-administrator[Manage RBAC authorizations]**: Grant permissions to users or groups and manage service accounts. +ifdef::openshift-enterprise,openshift-origin[] + - **xref:../applications/quotas/quotas-setting-per-project.adoc#quotas-setting-per-project[Set resource quotas]**: Choose from CPU, memory and other system resources to set quotas. +endif::[] + //// - **xref:../operators/crds/crd-managing-resources-from-crds.adoc#crd-managing-resources-from-crds[Manage resources from Custom Resource Definition (CRDs)]**: Learn about how {product-title} cluster administrators and project administrators can use CRDs to manage custom resources in non-default namespaces. ////