Skip to content

Commit c138417

Browse files
committed
osdocs-3212 Added a bullet to the Customer applications row.
Added the bullet point about providing a container image registry to ROSA docs. encouraging users to use latest supported API version.
1 parent 3442d02 commit c138417

File tree

3 files changed

+3
-1
lines changed

3 files changed

+3
-1
lines changed

modules/policy-customer-responsibility.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ The customer is responsible for the applications, workloads, and data that they
2727
* Create clusters with image pull secrets so that customer deployments can pull images from the Red Hat Container Catalog registry.
2828
* Provide access to OpenShift APIs that a customer can use to set up Operators to add community, third-party, and Red Hat services to the cluster.
2929
* Provide storage classes and plug-ins to support persistent volumes for use with customer applications.
30+
* Provide a container image registry so customers can securely store application container images on the cluster to deploy and manage applications.
3031
|* Maintain responsibility for customer and third-party applications, data, and their complete lifecycle.
3132
* If a customer adds Red Hat, community, third-party, their own, or other services to the cluster by using Operators or external images, the customer is responsible for these services and for working with the appropriate provider (including Red Hat) to troubleshoot any issues.
3233
* Use the provided tools and features to configure and deploy; keep up-to-date; set up resource requests and limits; size the cluster to have enough resources to run apps; set up permissions; integrate with other services; manage any image streams or templates that the customer deploys; externally serve; save, back up, and restore data; and otherwise manage their highly available and resilient workloads.

modules/policy-shared-responsibility.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,4 +165,4 @@ Disaster recovery includes data and configuration backup, replicating data and c
165165
|* Configure virtual networking connections with more than one tunnel where possible for protection against outages as recommended by the public cloud provider.
166166
* Maintain failover DNS and load balancing if using a global load balancer with multiple clusters.
167167

168-
|===
168+
|===

modules/rosa-policy-customer-responsibility.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ The customer is responsible for the applications, workloads, and data that they
2727
- Create clusters with image pull secrets so that customer deployments can pull images from the Red Hat Container Catalog registry.
2828
- Provide access to OpenShift APIs that a customer can use to set up Operators to add community, third-party, and Red Hat services to the cluster.
2929
- Provide storage classes and plug-ins to support persistent volumes for use with customer applications.
30+
- Provide a container image registry so customers can securely store application container images on the cluster to deploy and manage applications.
3031
|- Maintain responsibility for customer and third-party applications, data, and their complete lifecycle.
3132
- If a customer adds Red Hat, community, third-party, their own, or other services to the cluster by using Operators or external images, the customer is responsible for these services and for working with the appropriate provider, including Red Hat, to troubleshoot any issues.
3233
- Use the provided tools and features to configure and deploy; keep up to date; set up resource requests and limits; size the cluster to have enough resources to run apps; set up permissions; integrate with other services; manage any image streams or templates that the customer deploys; externally serve; save, back up, and restore data; and otherwise manage their highly available and resilient workloads.

0 commit comments

Comments
 (0)