Skip to main content

Responsibility Matrix - OpenShift Standard

Here is the RACI model defining the allocation of responsibilities between the client and Cloud Temple for the use of the OpenShift Standard service.

Definition of the different roles

We recall here the different RACI roles:

RoleDescription
(R) Responsible__R__esponsible for executing the process
(A) Accountable__A__ccountable for approving the process execution
(C) Consulted__C__onsulted during the process
(I) Informed__I__nformed of the process results (via tooling, the portal, or messaging)

Initial Setup

ActivityClient RoleCloud Temple Role
Define the overall OpenShift service architectureCRA
Size the OpenShift service (number of nodes, resources)CRA
Install the OpenShift service with default configurationIRA
OpenShift service configurationRAC
Configure the base network for the OpenShift serviceIRA
Deploy the initial identity and access configuration for OpenShiftCRA
Define the scaling and high availability strategy on the infrastructureCRA

Project and Application Management

ActivityClient RoleCloud Temple Role
Create and manage OpenShift projectsRAC
Deploy and manage applications in OpenShiftRAC
Configure CI/CD pipelinesRAC
Manage container images and registriesRAC

Maintenance and Updates

ActivityClient RoleCloud Temple Role
Update the OpenShift serviceRAI
Apply security patches to OpenShiftRAI
Update deployed applicationsRAI
Manage container image updatesRAI

Monitoring and Performance

ActivityClient RoleCloud Temple Role
Monitor OpenShift service performanceRAI
Monitor application performanceRAI
Manage OpenShift service alertsRAI
Manage application alertsRAI

Security

ActivityClient RoleCloud Temple Role
Manage OpenShift service securityRAI
Configure and manage pod security policiesRAC
Manage SSL/TLS certificates for the OpenShift serviceRAI
Manage SSL/TLS certificates for applicationsRAC
Implement and manage role-based access control (RBAC)RAI

Backup and Disaster Recovery

ActivityClient RoleCloud Temple Role
Define the backup strategy for the OpenShift serviceRACI
Implement and manage backups for the OpenShift serviceRACI
Define the backup strategy for the applicationsRACI
Implement and manage backups for the applicationsRACI
Test disaster recovery procedures for the serviceRACI
Test disaster recovery procedures for the applicationsRACI

Support and Issue Resolution

ActivityClient RoleCloud Temple Role
Provide Level 1 support for infrastructureIRA
Provide Level 2 and 3 support for infrastructureIRA
Resolve OpenShift service issuesRAC
Resolve application issuesRAC

Capacity Management and Evolution

ActivityClient RoleCloud Temple Role
Monitor OpenShift service resource usageRAC
Plan service capacity evolutionRAC
Implement capacity changesIRA
Manage application and resource evolutionRAC

Documentation and Compliance

ActivityClient RoleCloud Temple Role
Maintain OpenShift service documentationIRA
Maintain application documentationRAI
Ensure OpenShift service compliance with security standardsRAC
Ensure application compliance with security standardsRAC
Conduct OpenShift service auditsRAC
Conduct application auditsRAC

OpenShift Operators Management

OpenShift operators are service extensions that automate the management of complex applications or services on Kubernetes/OpenShift.

Under the OpenShift Standard service, no limitations on operators are enforced. Only the provision of the OperatorHub feature is ensured by Cloud Temple. Operators are made available via the Red Hat Marketplace catalog. The installation, monitoring, and management of updates for these operators are handled by the Client. The Client is responsible for using these operators to manage their workloads.

ActivityClient RoleCloud Temple Role
Provisioning of the default Operators catalogCIRA
Operators updatesRACI
Monitoring Operators statusRACI
Troubleshooting Operators issuesRACI
Managing Operators permissionsRACI
Managing Operators resources (ajout/suppression)RACI
Backing up Operators resources dataRACI
Supervision and monitoring of Operators resourcesRACI
Restoring Operators resources dataRACI
Operators security auditRACI
Operators supportRACI
Managing licenses and license contracts for operatorsRAI
Managing specific support plans for operatorsRAI

Important note :

  • Any damage caused by the installation of an operator or resulting from a client operation is the responsibility of the Client.
  • The management of licenses and specific support plans for operators is not the responsibility of Cloud Temple.

Clarification on Application Support

Application Support (Complementary Service) :

Application support regarding the development, configuration, management, and maintenance of applications is not the responsibility of Cloud Temple. The scope focuses solely on the management of the underlying infrastructure for the OpenShift service. Workload support, cluster management down to the operating system, operator management, and CI/CD pipelines are the responsibility of the client or any designated third-party provider for this task.

ActivityClient RoleCloud Temple Role
Application Support (Complementary Service)RAC