mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
Added OCE for 4.1 docs
This commit is contained in:
Vikram Goyal
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
7c3cf9cfc9
commit
ea8667df80
@@ -28,6 +28,9 @@ Distros: openshift-enterprise,openshift-origin,openshift-dedicated
|
||||
Topics:
|
||||
- Name: Welcome
|
||||
File: index
|
||||
- Name: About OpenShift Container Engine
|
||||
File: oce_about
|
||||
Distros: openshift-enterprise
|
||||
- Name: Accessing your services
|
||||
File: accessing-your-services
|
||||
Distros: openshift-dedicated
|
||||
|
||||
@@ -222,7 +222,7 @@ height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
|
||||
<h2>OpenShift Container Engine</h2>
|
||||
<div class="list-group">
|
||||
<p class="list-group-item-text">The OpenShift Container Engine is the core of the OpenShift Container Platform. Use OpenShift Container Platform docs links for OpenShift Container Engine documentation.</p>
|
||||
Read more about <a href="/container-platform/3.11/welcome/oce_about.html">OCE</a>.
|
||||
Read more about <a href="/container-platform/4.1/welcome/oce_about.html">OCE</a>.
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-sm-3 text-center">
|
||||
|
||||
404
welcome/oce_about.adoc
Normal file
404
welcome/oce_about.adoc
Normal file
@@ -0,0 +1,404 @@
|
||||
[[about_oce]]
|
||||
= About {oce}
|
||||
{product-author}
|
||||
{product-version}
|
||||
:oce: OpenShift Container Engine
|
||||
:data-uri:
|
||||
:icons:
|
||||
:experimental:
|
||||
:toc: macro
|
||||
:toc-title:
|
||||
|
||||
|
||||
Red Hat {oce} is a new product offering from Red Hat
|
||||
that lets you use {product-title} as a production platform for launching
|
||||
containers. You download and install {oce} in the same way as {product-title},
|
||||
but {oce} offers a subset of the features that {product-title} does.
|
||||
|
||||
[[about_oce_similarities_and_differences]]
|
||||
== Similarities and differences
|
||||
You can see the similarities and differences between {oce}
|
||||
and {product-title} in the following table:
|
||||
|
||||
.Product comparison for {oce} and {product-title}
|
||||
|===
|
||||
2+| |{oce} |{product-title}
|
||||
|
||||
2+h|Core Kubernetes and container orchestration
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Enterprise-ready configurations
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Standard infrastructure services
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Core user experience
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Maintained and curated content
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|OpenShift Container Storage compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Red Hat Middleware compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Serverless Cloud Functions compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Quay integration compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Container Native Virtualization for virtual machines compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Advanced cluster management
|
||||
|
|
||||
| X
|
||||
|
||||
2+h|Advanced networking
|
||||
|
|
||||
| X
|
||||
|
||||
2+h|Developer experience
|
||||
|
|
||||
| X
|
||||
|
||||
|===
|
||||
|
||||
[[about_oce_core_kubernetes_and_container_orchestration]]
|
||||
=== Core Kubernetes and container orchestration
|
||||
{oce} offers full access to an enterprise-ready Kubernetes
|
||||
environment that is easy to install and offers an extensive compatibility test
|
||||
matrix with many of the that software elements that you might use in your data
|
||||
center.
|
||||
|
||||
{oce} offers the same service level agreements, bug fixes, and common
|
||||
vulnerabilities and errors protection as {product-title}. {oce} includes a
|
||||
Red Hat Enterprise Linux Virtual Datacenter and Red Hat CoreOS entitlement that
|
||||
allows you to use an integrated Linux operating system with container runtime
|
||||
from the same provider.
|
||||
|
||||
{oce} is compatible with Windows Containers from Microsoft.
|
||||
|
||||
[[about_oce_enterprise_ready_configurations]]
|
||||
=== Enterprise-ready configurations
|
||||
{oce} uses the same security options and default settings as the {product-title}.
|
||||
Default security context constraints, pod security policies, best practice
|
||||
network and storage settings, service account configuration, SELinux integration,
|
||||
HAproxy edge routing configuration, and all other standard protections that
|
||||
{product-title} offers are available in {oce}. {oce} offers full access to the
|
||||
integrated monitoring solution that {product-title} uses, which is based on
|
||||
Prometheus and offers deep coverage and alerting for common Kubernetes issues.
|
||||
|
||||
{oce} uses the same installation and upgrade automation as {product-title}.
|
||||
|
||||
[[about_oce_standard_infrastructure_services]]
|
||||
=== Standard infrastructure services
|
||||
With an {oce} subscription, you receive support for all storage plug-ins that
|
||||
{product-title} supports.
|
||||
|
||||
In terms of networking, {oce} offers full and
|
||||
supported access to the Kubernetes Container Network Interface (CNI) and
|
||||
therefore allows you to use any third-party SDN that supports {product-title}.
|
||||
It also allows you to use the included Open vSwitch to establish a flat,
|
||||
non-project (Kubernetes namespace) segmented network for the Kubernetes cluster.
|
||||
{oce} allows customers to use a Kubernetes Network Policy to create
|
||||
microsegmentation between deployed application services on the cluster.
|
||||
|
||||
You can also use the route API objects that are found in {product-title},
|
||||
including its sophisticated integration with the HAproxy edge routing layer.
|
||||
|
||||
[[about_oce_core_user_experience]]
|
||||
=== Core user experience
|
||||
{oce} users have full access to Kubernetes Operators, pod deployment strategies,
|
||||
Helm, and {product-title} templates. {oce} users can use both the `oc` and
|
||||
`kubectl` command line interfaces. {oce} also offers an administrator web-based
|
||||
console that shows all aspects of the deployed container services and offers a
|
||||
container-as-a service experience. {oce} grants access to the Operator Life
|
||||
Cycle Manager that helps you control access to content on the cluster and life
|
||||
cycle operator-enabled services that you use. With an {oce} subscription, you
|
||||
receive access to the Kubernetes namespace, the OpenShift Project API object,
|
||||
and both cluster-level and tenant-level Prometheus monitoring metrics and events.
|
||||
|
||||
=== Maintained and curated content
|
||||
With an {oce} subscription, you receive access to the {product-title} entitled
|
||||
content from the Red Hat Container Catalog and Red Hat Connect ISV marketplace.
|
||||
You can access all maintained and curated content that the {product-title}
|
||||
eco-system offers either for free, such as the Red Hat Software Collections,
|
||||
or through additional purchases. The Kubernetes service broker, service catalog,
|
||||
and all {product-title} service broker offerings are supported with an
|
||||
{oce} subscription.
|
||||
|
||||
=== OpenShift Container Storage compatible
|
||||
{oce} is compatible and supported with OpenShift Container Storage.
|
||||
|
||||
=== Red Hat Middleware compatible
|
||||
{oce} is compatible and supported with Red Hat Middleware product solutions.
|
||||
|
||||
=== Serverless Cloud Functions compatible
|
||||
{oce} is compatible and supported with future Red Hat Cloud Functions products,
|
||||
such as function based and serverless container services.
|
||||
|
||||
=== Quay Integration compatible
|
||||
{oce} is compatible and supported with Red Hat Quay.
|
||||
|
||||
CNV VM Virtualization Compatible
|
||||
{oce} is compatible and supported with Red Hat product offerings derived from
|
||||
the kubevirt.io open source project.
|
||||
|
||||
=== Advanced cluster management
|
||||
A {oce} subscription does not offer a cluster-wide log aggregation
|
||||
solution or support ElasticSearch, Fluentd, Kibana based logging solutions.
|
||||
Similarly the chargeback features found in {product-title} and Red Hat Service
|
||||
Mesh capabilities derived from the open source Istio.io and kiali.io projects
|
||||
that offers OpenTracing observability for containerized services on
|
||||
{product-title} are not supported.
|
||||
|
||||
=== Advanced networking
|
||||
The standard networking solutions in {product-title} are not supported with an
|
||||
{oce} subscription. {product-title}’s Kubernetes CNI plug-in for automation of
|
||||
multi-tenant network segmentation between {product-title} projects is not
|
||||
entitled for use with {oce}. {product-title} offers more granular control of the
|
||||
source IP addresses that are used by application services on the cluster.
|
||||
Those egress IP address controls are not entitled for use with {oce}.
|
||||
{product-title} offers ingress routing to on cluster services that use
|
||||
non-standard ports when no public cloud provider is in use via the VIP pods
|
||||
found in {product-title}. That ingress solution is not supported in {oce}.
|
||||
{oce} users are supported for the Kubernetes ingress control object, which
|
||||
offers integrations with public cloud providers. Red Hat Service Mesh, which is
|
||||
derived from the istio.io open source project, is not supported in {oce}.
|
||||
|
||||
=== Developer experience
|
||||
With {oce}, the following capabilities are not supported:
|
||||
|
||||
* The developer experience utilities and tools.
|
||||
* {product-title}’s pipeline feature that integrates a streamlined,
|
||||
Kubernetes-enabled Jenkins experience in the user’s project space.
|
||||
* The {product-title}’s source-to-image feature, which allows you to easily
|
||||
deploy source code, dockerfiles, or container images across the cluster.
|
||||
* Build strategies, builder pods, or imagestreams for end user container
|
||||
deployments.
|
||||
* The `odo` developer command line.
|
||||
* The developer persona in the {product-title} web console.
|
||||
|
||||
=== Feature summary
|
||||
|
||||
The following table is a summary of the feature availability in {oce} and
|
||||
{product-title}.
|
||||
|
||||
.Features in {oce} and {product-title}
|
||||
|===
|
||||
2+| |{oce} |{product-title}
|
||||
|
||||
2+h|Core Kubernetes and container orchestration
|
||||
h| X
|
||||
h| X
|
||||
|
||||
.3+|
|
||||
| Enterprise-class Kubernetes
|
||||
| X
|
||||
| X
|
||||
|
||||
| Red Hat Enterprise Linux for Virtual Datacenters and Red Hat CoreOS
|
||||
| X
|
||||
| X
|
||||
|
||||
| Windows containers compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Enterprise-ready configurations
|
||||
h| X
|
||||
h| X
|
||||
|
||||
.3+|
|
||||
| Complete life-cycle automation of platform
|
||||
| X
|
||||
| X
|
||||
|
||||
|
||||
| Management, monitoring, alerting, and remedy through Prometheus
|
||||
| X
|
||||
| X
|
||||
|
||||
|
||||
| Enterprise-ready security
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Standard infrastructure services
|
||||
h| X
|
||||
h| X
|
||||
|
||||
.3+|
|
||||
| Edge routing
|
||||
| X
|
||||
| X
|
||||
|
||||
|
||||
| Flat networking
|
||||
| X
|
||||
| X
|
||||
|
||||
|
||||
| Kubernetes storage plug-ins
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Core user experience
|
||||
h| X
|
||||
h| X
|
||||
|
||||
.6+|
|
||||
| Application deployments, deployment configuration, templates, and Operators
|
||||
| X
|
||||
| X
|
||||
|
||||
| Administrator console
|
||||
| X
|
||||
| X
|
||||
|
||||
| Operator life cycle management
|
||||
| X
|
||||
| X
|
||||
|
||||
| kubectl command line
|
||||
| X
|
||||
| X
|
||||
|
||||
| Developer projects
|
||||
| X
|
||||
| X
|
||||
|
||||
| Prometheus metrics
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Maintained and curated content
|
||||
h| X
|
||||
h| X
|
||||
|
||||
.3+|
|
||||
| Red Hat Container Catalog access
|
||||
| X
|
||||
| X
|
||||
|
||||
| Independent Software Vendor and partner Operator access
|
||||
| X
|
||||
| X
|
||||
|
||||
| Service Catalog and Brokers for cloud content
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Red Hat add-ons
|
||||
h|
|
||||
h| X
|
||||
|
||||
.6+|
|
||||
| OpenShift Container Storage compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
| Red Hat Middleware compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
| Serverless Cloud Functions compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
| Istio runtime launchers compatible
|
||||
|
|
||||
| X
|
||||
|
||||
| Quay integration compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
| Container Native Virtualization for virtual machines compatible
|
||||
| X
|
||||
| X
|
||||
|
||||
2+h|Advanced cluster management
|
||||
h|
|
||||
h| X
|
||||
|
||||
.3+|
|
||||
| Logging
|
||||
|
|
||||
| X
|
||||
|
||||
| Chargeback
|
||||
|
|
||||
| X
|
||||
|
||||
| Kiali (Jaeger and OpenTracing)
|
||||
|
|
||||
| X
|
||||
|
||||
2+h|Advanced networking
|
||||
h|
|
||||
h| X
|
||||
|
||||
.4+|
|
||||
| Egress per pod or namespace
|
||||
|
|
||||
| X
|
||||
|
||||
| Ingress for non-standard ports
|
||||
|
|
||||
| X
|
||||
|
||||
| Multi-tenant SDN
|
||||
|
|
||||
| X
|
||||
|
||||
| Red Hat Service Mesh (Istio)
|
||||
|
|
||||
| X
|
||||
|
||||
2+h|Developer experience
|
||||
h|
|
||||
h| X
|
||||
|
||||
.4+|
|
||||
| Integrated CI/CD pipelines
|
||||
|
|
||||
| X
|
||||
|
||||
| Source-to-Image Container factory
|
||||
|
|
||||
| X
|
||||
|
||||
| odo command line
|
||||
|
|
||||
| X
|
||||
|
||||
| Developer console
|
||||
|
|
||||
| X
|
||||
|
||||
|===
|
||||
|
||||
|
||||
== Subscription Limitations
|
||||
|
||||
{oce} is a subscription offering that provides {product-title} with a limited set
|
||||
of supported features at a lower list price. {oce} and {product-title} are the
|
||||
same product and, therefore, all software and features are delivered in both.
|
||||
There is only one download, {product-title}. {oce} uses the {product-title}
|
||||
documentation and support services and bug errata for this reason.
|
||||
Reference in New Issue
Block a user