-
Notifications
You must be signed in to change notification settings - Fork 67
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
CRD changes can’t easily be tested in the operator #2857
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
Talking about this on the scrub, it doesn't seem like this would do a lot to help with RBAC (which is what changes most frequently). The project where the RBAC is actually used, say Submariner's main repo, would still need a second PR after the RBAC changes to actually test them where they are used. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
CRD changes to the types managed by the operator can’t easily be tested because the CRDs are installed by
subctl
. The version ofsubctl
used notably in operator E2E isn’t rebuilt with the version of the operator being tested, so it doesn’t have the CRD changes (or RBAC etc.).One possible fix for this (other than rebuilding
subctl
— which isn’t great because it means the operator project has knowledge of a specific dependent) would be to update the CRDs using the operator versions after initial deployment.The text was updated successfully, but these errors were encountered: