MCPServer: allow default image injection (npx/uvx) and set Healthy wh… #85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…en pods ready; add logs Signed-off-by: Anurag Ojha <[email protected]>
Signed-off-by: Anurag Ojha <[email protected]>
intojhanurag
force-pushed
the
fix/mcpserver-default-image-health
branch
from
565157d to
4394a4c
Compare
|
Hey @jmhbh @rinormaloku , this is ready for review |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #76 a bug where MCPServer resources that use cmd: npx (or uvx) stay in Unhealthy state unless spec.deployment.image is explicitly set.
Now, the controller correctly injects a default image (node:24-alpine3.21) during translation, and the status is updated to Healthy.