MCPServer: Enforce Kong entities Spec
- Dominant language
- Go
- Stars
- 109
- Forks
- 49
- Avg merge
- 21h 28m
- Merged PRs (30d)
- 313
Description
## Problem Statement
As part of the `MCPServer` reconciliation loop, we create some Kong entities. We need to continuously enforce their spec in the Kubernetes resources (and as a side effect in Konnect).
## Acceptance Criteria
- [ ] `KongService`s owned by `MCPServer`s have their spec enforced
- [ ] `KongRoute`s owned by `MCPServer`s have their spec enforced
- [ ] `KongPlugin`s owned by `MCPServer`s have their spec enforced
- [ ] `KongPluginBinding`s owned by `MCPServer`s have their spec enforced
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the MCPServer reconciliation loop and how it creates the owned KongService, KongRoute, KongPlugin, and KongPluginBinding resources. Verify the existing tests around reconciliation before changing behavior. Done means each listed resource continuously has its spec enforced in Kubernetes, with the corresponding Konnect side effect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100