operator-framework
Provide a way to modify how a field appears for a CRD/APIs that the package owner do not control
It has been mentioned in the past that my team's operator is less than ideal.
it seems less then ideal to have an operator install another operator and manage the dependent CRD's.
It is not always possible or desired to be the owner of every CRD / go_types.go an operator will deploy. Not all upstream projects we want available as a package want to use the same packaging ecosystem.
Many upstream kubernetes project have already chosen that they will only do helm charts or install via CLI etc.
Our team are making available a package that would otherwise not be on the platform's marketplace, it should be easy to make visual or packaging changes without having to own or define everything in a CRD we own.
Please keep us in mind as this seems to be a potential replacement of operator-sdk.
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.