anchor.diff:  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.
   
  +- **Deploy Helm Charts**: 
  +xref:../cli_reference/helm-cli/getting-started-with-helm-on-openshift-container-platform.html[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. 
  +
   - **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.
   
   - **xref:../builds/understanding-image-builds.adoc#understanding-image-builds[Understand image builds]**: Choose from different build strategies (Docker, S2I, custom, and pipeline) that can include different kinds of source materials (from places like Git repositories, local binary inputs, and external artifacts). Then, follow examples of build types from basic builds to advanced builds.
   
  -- **xref:../openshift_images/images-understand.adoc#understanding-images[Create container images]**: A container image is the most basic building block in OpenShift (and Kubernetes) applications. Defining imagestreams lets you gather multiple versions of an image in one place as you continue its development. S2I containers let you insert your source code into a base container that is set up to run code of a particular type (such as Ruby, Node.js, or Python).
  +- **xref:../openshift_images/images-understand.adoc#understanding-images[Create container images]**: A container image is the most basic building block in {product-title} (and Kubernetes) applications. Defining imagestreams lets you gather multiple versions of an image in one place as you continue its development. S2I containers let you insert your source code into a base container that is set up to run code of a particular type (such as Ruby, Node.js, or Python).
   
   - **xref:../applications/deployments/what-deployments-are.adoc#what-deployments-are[Create Deployments and DeploymentConfigs]**:  Use Deployments and DeploymentConfigs to exert fine-grained management over applications.
   Use the Workloads page or `oc` CLI to xref:../applications/deployments/managing-deployment-processes.adoc#deployment-operations[manage DeploymentConfigs]. Learn xref:../applications/deployments/deployment-strategies.adoc#deployment-strategies[Rolling, Recreate, and Custom] deployment strategies.
  
positive.code: ifdef::openshift-enterprise,openshift-origin[]
  - **xref:../operators/operator_sdk/osdk-getting-started.adoc#osdk-getting-started[Create Operators]**: Operators are the preferred method for creating on-cluster applications for {product-title} {product-version}. Learn the workflow for building, testing, and deploying Operators. Then create your own Operators based on xref:../operators/operator_sdk/osdk-ansible.adoc#osdk-ansible[Ansible] or
  xref:../operators/operator_sdk/osdk-helm.adoc#osdk-helm[Helm], or configure xref:../operators/operator_sdk/osdk-monitoring-prometheus.adoc#osdk-monitoring-prometheus[built-in Prometheus monitoring] using the Operator SDK.
  
  - **Use xref:../applications/service_brokers/installing-template-service-broker.adoc#sb-about-template-service-broker-sb-installing-tsb[Template Service Broker] or xref:../applications/service_brokers/installing-ansible-service-broker.html#sb-about-ansible-service-broker-sb-installing-asb[OpenShift Ansible Broker] applications**: Service brokers are a mechanism for provisioning applications outside of an {product-title} environment.
  endif::[]
  
negative.code: xref:../authentication/identity_providers/configuring-htpasswd-identity-provider.adoc#configuring-htpasswd-identity-provider[HTPasswd],
  xref:../authentication/identity_providers/configuring-keystone-identity-provider.adoc#configuring-keystone-identity-provider[Keystone],
  xref:../authentication/identity_providers/configuring-ldap-identity-provider.adoc#configuring-ldap-identity-provider[LDAP],
  xref:../authentication/identity_providers/configuring-basic-authentication-identity-provider.adoc#configuring-basic-authentication-identity-provider[basic authentication],
  xref:../authentication/identity_providers/configuring-request-header-identity-provider.adoc#configuring-request-header-identity-provider[request header],
  xref:../authentication/identity_providers/configuring-github-identity-provider.adoc#configuring-github-identity-provider[GitHub],
  xref:../authentication/identity_providers/configuring-gitlab-identity-provider.adoc#configuring-gitlab-identity-provider[GitLab],
  xref:../authentication/identity_providers/configuring-google-identity-provider.adoc#configuring-google-identity-provider[Google],
  and
  xref:../authentication/identity_providers/configuring-oidc-identity-provider.adoc#configuring-oidc-identity-provider[OpenID].
  
  - **Manage xref:../authentication/certificates/replacing-default-ingress-certificate.adoc#replacing-default-ingress[Ingress], xref:../authentication/certificates/api-server.adoc#api-server-certificates[API server], and xref:../authentication/certificates/service-serving-certificate.adoc#add-service-serving[service] certificates**: {product-title} creates certificates
  by default for the Ingress Operator, the API server, and for
  