Add RCO system requirements to v1 doc #634
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
leochr
reviewed
Aug 16, 2024
doc/user-guide-v1.adoc
Outdated
|
|
||
| ==== OCP requirements | ||
|
|
||
| Runtime Component operator requires an link:++https://docs.openshift.com/container-platform/4.15/welcome/index.html++[OCP version 4.15], link:++https://docs.openshift.com/container-platform/4.14/welcome/index.html++[OCP version 4.14], or link:++https://docs.openshift.com/container-platform/4.12/welcome/index.html++[OCP version 4.12] cluster on Linux x86_64 (amd64), Linux on Power (ppc64le), or Linux on IBM Z (s390x) platform, with cluster-admin permissions. To manage OCP projects with OCP CLI (oc) commands, the installation also requires the link:++https://docs.openshift.com/container-platform/4.9/cli_reference/openshift_cli/getting-started-cli.html++[OCP CLI]. |
There was a problem hiding this comment.
Add OCP version 4.16 (https://docs.openshift.com/container-platform/4.16/welcome/index.html) to the list
doc/user-guide-v1.adoc
Outdated
| If you are installing a Runtime Component operator on a Kubernetes cluster, your environment must meet the Kubernetes cluster requirements. | ||
|
|
||
| ==== Kubernetes requirements | ||
| Runtime Component operator requires a Kubernetes version 1.28, 1.27, 1.26, or 1.25 cluster on Linux x86_64 (amd64), Linux on Power (ppc64le), or Linux on IBM Z (s390x) platform, with cluster-admin permissions. |
doc/user-guide-v1.adoc
Outdated
|
|
||
| Your environment might need to meet certain storage requirements when you use Runtime Component operator. | ||
|
|
||
| No storage requirements exist for Runtime Component operator. However, if you are using the Runtime Component operator serviceability feature, and you have applications with multiple replicas, storage must support `ReadWriteMany` access mode. For more information, see link:#storage-for-serviceability[Storage for serviceability]. |
There was a problem hiding this comment.
Serviceability storage is specific to Liberty Operators and doesn't apply to RCO. So we should exclude the following in RCO:
However, if you are using the Runtime Component operator serviceability feature, and you have applications with multiple replicas, storage must support `ReadWriteMany` access mode. For more information, see link:#storage-for-serviceability[Storage for serviceability].
There was a problem hiding this comment.
Updated and I removed
Your environment might need to meet certain storage requirements when you use Runtime Component operator.
as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.