-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
OpenShift 4.0
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1] Proposed title of this feature request
-> Request to Promote redhat-cop Operators to Fully Supported Status in OpenShift
2] What is the nature and description of the request?
-> Request to maintain the operators from redhat-cop (community of practise) being promoted to being fully supported operators in OpenShift
We find the following operators very useful, in order from most useful to less. Please maintain (ie, update, cut-releases, watch for CVE) these operators
- https://github.com/redhat-cop/namespace-configuration-operator
- https://github.com/redhat-cop/group-sync-operator
- https://github.com/redhat-cop/volume-expander-operator
- https://github.com/redhat-cop/cert-utils-operator/
They were initially created by redhat - and customers now use them, but they are not well maintained - so builds age with accumulating CVEs.
3] Why does the customer need this? (List the business requirements here)
Business cases:
- The namespace configuration operator is very useful to template and generate resources on the fly based on labelling on namespaces. This is useful from a platforming perspective to provide a cohesive starting set of resources to developers, like initial install of operators, quotas, role-bindings.
- The group sync operator is useful for organizations that already rely on IDPs like azure entra, because they can sync in existing team- and organizational structure data as groups and use these for rolebindings in the cluster - thus removing overhead.
- The volume-expander operator is useful to automatically expand volumes and hence reduce toil and strain on platforming teams and reduce chance of volumes un-attended running full and causing downtime.
- The cert-utils operator is mainly useful to automatically generate metadata in order to work with certificates more easily - especially for novice users it might be somewhat tricky to deal with yaml extraction and base64 encoding.
4] List any affected packages or components.
Affected packages: