Summary

As an OpenShift customer I would like to be able to provide my must gather information to support.  However, due to internal security requirements, the data provided must be obfuscated in order for it to be sent to outside parties.  

Data may include things like ip addresses, secrets, config maps.  However, as a customer, I would also like the flexibility to target specific textual data for replacement.

Out of Scope

Deliverables

• Design of obfuscation tool
• Tool that can take a must gather as input and produce an obfuscated version as output
• CI tooling to test obfuscation
• Documentation for obfuscation tool
• Required image/release pipelines for tool

Dependencies

This tool should be designed in conjunction with the Px team, who owns the must gather repository and the workloads team who owns oc.

Open Questions

1. ....  

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>