-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Sync for manifests and helm chart #564
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great to me (just a couple of grammar nits),
any thoughts @Jeffwan @scarlet25151?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Co-authored-by: Dmitri Gekhtman <[email protected]> Signed-off-by: Kai-Hsun Chen <[email protected]>
Co-authored-by: Dmitri Gekhtman <[email protected]> Signed-off-by: Kai-Hsun Chen <[email protected]>
Nice! Do we still need a PR with some logic to keep RBAC in sync? |
Oh, I think we need RBAC synchronization. I will open an issue. |
The CRD inconsistency between ray-operator/config/crd/bases/ and helm-chart/kuberay-operator/crds/ is possible to cause bugs like ray-project#538. Hence, we need to check the consistency in GitHub Actions. Signed-off-by: Kai-Hsun Chen <[email protected]>
Why are these changes needed?
The CRD inconsistency between
ray-operator/config/crd/bases/
andhelm-chart/kuberay-operator/crds/
is possible to cause bugs like #538. Hence, we need to check the consistency in GitHub Actions.Related issue number
Closes #446
#538
Checks
#565 is the control group.