Skip to content

Controller updates Deployment/Service specs without checking ownership #85

@aliok

Description

@aliok

Originated from #83 (comment)

The MCPServer controller updates Deployments and Services based on name lookup only, without validating ownership before modifying resources. This can lead to "controller wars" where multiple controllers fight over the same resources.

Current Behavior

When reconciling an MCPServer resource:

  1. Deployment/Service names are set to exactly match the MCPServer name (no prefix/suffix/random text)
    • MCPServer my-server → Deployment my-server, Service my-server
  2. Resource lookup is done by name only
  3. No ownership check before updating
  4. The controller silently overwrites the spec even if another controller owns the resource

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions