You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few operator PRs out right now - #141 and #152 immediately come to mind, that raise some questions.
What is the policy for our primary operator repository on the contents of this repository and what that implies as far as ownership and support? Is the maintainer listed in the operator.yaml the contact for issue reporting and PRs? Is the KUDO team? Someone else? What is allowed into the operators repo? What is not? What gets tested?
Helm has a large chart repo and not all charts are actively maintained. They're even moving to a more federated approach instead of having a single repository of all charts.
This policy needs to account for all operators, including ones that the KUDO team spend their time on.
The text was updated successfully, but these errors were encountered:
We have a few operator PRs out right now - #141 and #152 immediately come to mind, that raise some questions.
What is the policy for our primary operator repository on the contents of this repository and what that implies as far as ownership and support? Is the
maintainer
listed in the operator.yaml the contact for issue reporting and PRs? Is the KUDO team? Someone else? What is allowed into the operators repo? What is not? What gets tested?Helm has a large chart repo and not all charts are actively maintained. They're even moving to a more federated approach instead of having a single repository of all charts.
This policy needs to account for all operators, including ones that the KUDO team spend their time on.
The text was updated successfully, but these errors were encountered: