mathieu-benoit / mathieu-benoit/score-openchoreo
Create `dns` and `route` resource provisioners
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Create `dns` and `route` resource provisioners, apparently just `visibility: [external]` like illustrated here: https://github.com/openchoreo/openchoreo/blob/main/samples/gcp-microservices-demo/components/frontend-component.yaml#L30C7-L30C29.
Contributor guide
No contributing guide indexed for this repository
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 with the referenced samples/gcp-microservices-demo/components/frontend-component.yaml example, especially the visibility setting, then inspect how existing resource provisioners are represented in score-openchoreo. Add dns and route provisioners with the requested external visibility and verify that generated OpenChoreo manifests include both resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100