Epic Goal

• This epic is focusing on making sure that our Rolling Demo instance is secure and we have all the tools available to monitor it

Why is this important?

• Rolling Demo started as an one-off solution for RH Summit 2025, but now it has become an important part of our release cylce. It is used to showcase our work, experiment etc.
• That said we should invest time to ensure that everything works fine and as expected, while we also guarantee that security is at a sufficient level

Scenarios

1. Log Forwarding: Ideally we should have a solution for log forwarding that will enable us to monitor the different services we have running on our dev cluster.
2. Token Rotation: Our RHDH instances are using a number of tokens for themselves and other services they are connected with. We need to make sure that we have a mechanism in place that takes care of their rotation.
3. Secret Maintenance: Until we have a permanent solution for token rotation we could check the current status and see if we need to clean or renew any secrets

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Logs from dev Cluster are forwarded to a service of our choice, enabling us to monitor the lifecycle of all important services.
• Not needed secrets are cleaned and existing tokens are rotated.
• A new mechanism for token rotation is in place.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment