-
Notifications
You must be signed in to change notification settings - Fork 0
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: inference-gateway/operator
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.8.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: inference-gateway/operator
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.9.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 22 files changed
- 2 contributors
Commits on Jun 27, 2025
-
docs(fix): Correct emoji rendering in API Overview section of README
Signed-off-by: Eden Reich <eden.reich@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 0481b4f - Browse repository at this point
Copy the full SHA 0481b4fView commit details
Commits on Jun 28, 2025
-
feat: Implement MCP (Model Context Protocol) resource and controller …
…with RBAC roles (#12) * feat: Implement MCP (Model Context Protocol) resource and controller with RBAC roles Signed-off-by: Eden Reich <eden.reich@gmail.com> * feat: Add MCP server configuration with namespace and specifications Would be cool to just have a side-car container that ensures those STDIO MCP servers can also support SSE or any streamable HTTP. Some MCPs supports only STDIO. which makes it complex to connect to in a containerized environment. Meaning you would normally have to create a custom bridge (web server) that sends a command to the internal process - not ideal, but it-is what it-is. Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: Update MCP image reference to use the correct repository I'm not going to host those servers registry, I think it would be easier to just use the existing ones. Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: Ensure consistent TLS secret name in MCP ingress configuration Signed-off-by: Eden Reich <eden.reich@gmail.com> * feat: Enhance MCP configuration with server, bridge, ingress, and TLS specifications Signed-off-by: Eden Reich <eden.reich@gmail.com> * feat: Add Horizontal Pod Autoscaler (HPA) configuration for MCP server - Introduced HPA configuration under the MCP server spec, allowing for dynamic scaling based on defined metrics. - Added properties for scaling behavior, including scaleUp and scaleDown policies, stabilization windows, and metrics specifications. - Updated image and replicas fields to provide defaults and descriptions for better clarity. - Removed deprecated ingress configuration and replaced it with HPA-specific settings to streamline deployment management. Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: WIP - update import statements and logger usage in MCP controller I think I should stick to standard MCP using node life time support server, and if the user wants they can configure their own container image, this allows more flexibility. Depending on what's configured option is used the package will take precedence over the image. Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: Start with implementing the official way of running MCP servers, then will switch to custom MCPs Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: Remove unused ingress configuration from MCP server YAML I think ingress doesn't make a lot of sense in the context of MCP, normally those are server you would like to run internally. I don't think there is a use-case to expose it to the outside world. Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: Remove unnecessary comment in shouldWatchNamespace function Signed-off-by: Eden Reich <eden.reich@gmail.com> * test: Add basic tests Signed-off-by: Eden Reich <eden.reich@gmail.com> * fix: Remove unnecessary variable declaration in MCP controller test Signed-off-by: Eden Reich <eden.reich@gmail.com> * refactor: Simplify fields Building a generic bridge for all Stdio servers is too complex. I'll just create a registry for MCP servers written in golang so people can pull them. Will add the essential ones like filesystem context7. Just need to build those containers and push them to registry so it's possible to pull them and run them as a streamable http that supports also https. I think the default npx -y with the modelcontext protocol lake of production settings. Signed-off-by: Eden Reich <eden.reich@gmail.com> * feat: Enhance MCP Controller Tests and CRD Definitions - Refactored MCP controller tests to use DescribeTable for better organization and readability. - Added additional test cases for various reconciliation scenarios, including handling of HPA and service reconciliation. - Updated CRD definitions to include additional printer columns for MCP resources, displaying the URL of the MCP server and the resource age. - Modified the schema to support an array type for the command field in the MCP spec. - Added a new field in the status to store the URL of the MCP server. Signed-off-by: Eden Reich <eden.reich@gmail.com> * chore: Update test coverage badge to reflect current coverage Signed-off-by: Eden Reich <eden.reich@gmail.com> --------- Signed-off-by: Eden Reich <eden.reich@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for ee8c869 - Browse repository at this point
Copy the full SHA ee8c869View commit details -
Configuration menu - View commit details
-
Copy full SHA for 780ca51 - Browse repository at this point
Copy the full SHA 780ca51View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.8.0...v0.9.0