-
Notifications
You must be signed in to change notification settings - Fork 83
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
fix: rename CheClusterStatus structure to bypass bug in operator-sdk #870
Conversation
Signed-off-by: Anatolii Bazko <abazko@redhat.com>
Signed-off-by: Anatolii Bazko <abazko@redhat.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: AndrienkoAleksandr, metlos, tolusha The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test v7-devworkspace-happy-path |
/test v7-stable-to-nightly |
I applied linked issue to the pull request description operator-framework/operator-sdk#4990 |
/test v7-devworkspace-happy-path |
@tolusha: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/test v7-devworkspace-happy-path |
Signed-off-by: Anatolii Bazko abazko@redhat.com
What does this PR do?
Accordingly to @AndrienkoAleksandr investigation, operator-sdk v1.7.x and v1.8.x versions contain bug in parser which prevents it from building a new bundle (it start consuming all available memory). See more: operator-framework/operator-sdk#4990.
Rename CheClusterStatus structure to bypass bug in operator-sdk
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
eclipse-che/che#19466
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.