-
Notifications
You must be signed in to change notification settings - Fork 38
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
✨ Replace windup with analyzer-lsp #249
Conversation
Fixes konveyor#244 Signed-off-by: David Zager <[email protected]>
Looks like the pod starts:
Not sure if there is anything more to do at this point to verify it's working from the operator's perspective. |
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, I'd argue we dont need limits by default. Dont feel too strongly though.
hub_container_limits_memory: "800Mi" | ||
hub_container_requests_cpu: "100m" | ||
hub_container_requests_memory: "350Mi" | ||
hub_container_limits_cpu: "1" |
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.
@djzager do we really need limits?
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.
Seems like we should have a limit to be a good citizen on the cluster. That said, I don't know if 1 core is appropriate for out-of-the-box but felt sure that 100m was not enough.
|
Signed-off-by: David Zager <[email protected]>
Signed-off-by: David Zager <[email protected]>
Signed-off-by: David Zager <[email protected]>
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
This reverts commit 21e7d16.
This reverts commit 21e7d16. Signed-off-by: David Zager <[email protected]>
Fixes #244