openmcp-project / openmcp-project/backlog
Task: replace platform service DNS with HelmDeployment
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Understand the Task
Description
The sole purpose of platform service DNS is to deploy external-dns onto different clusters. This can easily be expressed by a HelmDeployment.
The advantage is that we could drop the platform service DNS completely and would only need to maintain a single, static YAML manifest instead of a whole controller.
Any further valuable resources.
No response
What is required to accept the Task as done.
Done Criteria
- Design
HelmDeploymentto produce results equivalent to running platform service DNS. - Remove platform service DNS from landscapes.
- Remove deployed external-dns from clusters.
- Deleting the platform service does not remove its installed external-dns deployments. This either needs to be done manually, or the platform service's configuration is changed so that the cluster selector does not match any
Clusterresources anymore, then the platform service should clean up its deployed instances on its own.
- Deleting the platform service does not remove its installed external-dns deployments. This either needs to be done manually, or the platform service's configuration is changed so that the cluster selector does not match any
- Remove deployed external-dns from clusters.
- Roll out HelmDeployment on landscapes and verify that it deploys external-dns with correct configuration.
- Include external-dns in OCM umbrella component, if that is not already done.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the existing platform service DNS deployment and HelmDeployment behavior across the landscapes. Replace it with equivalent external-dns deployment and configuration, remove the old service and instances, roll out the replacement, and verify external-dns plus its OCM umbrella component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100