WHAT

What mechanism could be used to "suspend" a RHOSAK instance e.g. scale down all associated pods or remove the instance but keep the PVs. suspend in this context is a way to no longer consume compute resources but keep the data for the RHOSAK instance.

The second part is restoring a suspended RHOSAK instance to a working state e.g. scale the pods or create the instance with the existing PVs. In the case of restoration, the kafka id, routes etc should all be the same as they were before the suspension.

This JIRA is to investigate how this could be done, ideally with a POC as the outcome.

WHY

Suspension is useful on termination of a customer's subscription entitlement or non-payment where it may have been a mistake. It could also be exposed to customers in the future as a feature.

HOW

<Suggestions for how this may be solved.> [Optional]

DONE

Include the following where applicable:

• Documented the options for suspension and restoration of a RHOSAK instance
• [Optional] POC of the most likely chosen option

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged