CQA WLC-1: OpenShift Overviews and Editions#114761
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@mburke5678: This pull request references WLC-1 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
Bot
added
the
size/XL
| // Module included in the following assemblies: | ||
| // | ||
| // * getting_started/kubernetes-overview.adoc | ||
|
|
There was a problem hiding this comment.
Created a new module for text that came after an include. See kubernetes-overview.adoc, line 30
|
|
||
| You can see the similarities and differences in the following table: | ||
|
|
||
| .Product comparison for {oke} and {product-title} |
There was a problem hiding this comment.
Moved from https://github.com/openshift/openshift-docs/pull/114761/changes#diff-fb0dd1ddb0a4914420174307c8628add49ad7ac636ff7f202565159f8e663df3L27 to avoid lower-level headings errors.
NO CHANGES TO THE TEXT EXCEPT FOR VALE ERRORS AS REPORTED BELOW. NO NEED TO REVIEW.
| image::247_OpenShift_Kubernetes_Overview-2.png[] | ||
|
|
||
| A cluster is a single computational unit consisting of multiple nodes in a cloud environment. A Kubernetes cluster includes a control plane and worker nodes. You can run Kubernetes containers across various machines and environments. The control plane node controls and maintains the state of a cluster. You can run the Kubernetes application by using worker nodes. You can use the Kubernetes namespace to differentiate cluster resources in a cluster. Namespace scoping is applicable for resource objects, such as deployment, service, and pods. You cannot use namespace for cluster-wide resource objects such as storage class, nodes, and persistent volumes. | ||
| include::modules/kubernetes-architecture.adoc[leveloffset=+1] |
There was a problem hiding this comment.
Moved the text into the kubernetes-architecture.adoc module.
| {oke} is a subscription offering that provides {product-title} with a limited set | ||
| of supported features at a lower list price. {oke} and {product-title} are the | ||
| same product and, therefore, all software and features are delivered in both. | ||
| There is only one download, {product-title}. {oke} uses the {product-title} | ||
| documentation and support services and bug errata for this reason. |
There was a problem hiding this comment.
Moved here from the end of the assembly for better flow.
| toc::[] | ||
|
|
||
| [role="_abstract"] | ||
| You can use the Red Hat {oke} as a way to launch containers in an enterprise-class Kubernetes production platform. |
mburke5678
added
the
merge-review-needed
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
4 participants
https://redhat.atlassian.net/browse/OSDOCS-16952
Previews:
Learn more about OpenShift Container Platform
Introduction to OpenShift Container Platform
Kubernetes overview
Red Hat OpenShift editions
About OpenShift Kubernetes Engine