Skip to content

Splitting the MCPRegistry CRD #288

Description

@rdimitrov

This one potentially affects also the responsibilities of the Operator & the Registry in relation to k8s features

Note that this one may probably be unnecessary given we'll have the ability to manage registries via the API, so leaving it as a placeholder to collect enough signals if it's needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions