Implement Service Provider Flux
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
Research direction
Start with the service-provider-flux repository and read control-plane-operator/pkg/controlplane/components/flux_component.go to understand the Juggler approach. Map the new Flux instance resource and pipeline initialization before planning tests. Done means installation, update, deletion, documentation, unit tests, and integration coverage meet the listed criteria and pass review.
Written by the indexing model from the issue text.
Description
Understand the Task
Description
Implement a new service provider for Flux, based on the MCP Architecture V2.
The Service Provider Flux should be able to install/update/delete Flux instances on Managed Control Planes.
https://github.com/openmcp-project/service-provider-flux
To accomplish this, we will use the carve-out-approach in the first round, see https://github.com/openmcp-project/backlog/issues/199
What is required to accept the Task as done.
Implementation
- The service-provider-flux manages a new "Flux" instance resource
- Uses the Juggler approach for handling Flux installation, see https://github.com/openmcp-project/control-plane-operator/blob/main/pkg/controlplane/components/flux_component.go
- Initialize Pipeline
- prepare open source
- Write tests
Done Criteria
- Finish implementation
- Code has been reviewed by other team members
- Internal technical Documentation created/updated
- New / changed code is documented
- Unit Tests created for new code or existing Unit Tests updated
- Integration Test Suite updated
- Enduser Documentation updated (if applicable)
- Successful demonstration in Review
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from openmcp-project/backlog
-
area/webapp kind/feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openmcp-project/backlog#700 ·
-
kind/task needs/validation sig/extensibility
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openmcp-project/backlog#699 ·
-
kind/task needs/validation sig/extensibility
Difficulty 1/5 Under an hour Newbie friendliness 68/100
openmcp-project/backlog#697 ·
-
area/webapp
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openmcp-project/backlog#656 ·
-
area/webapp
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openmcp-project/backlog#654 ·
All issues in openmcp-project/backlog
Similar issues
-
kind/bug Ubuntu 24
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kubernetes-sigs/kubespray#13532 ·
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elementary/flatpak-platform#253 ·
-
tagbot-manual
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100