openmcp-project / openmcp-project/backlog

Epic: Custom CA support for remaining service providers

Open
#613 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/epic needs/validation
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Understand the Epic

The goal of this epic is to provide support for custom CA certificates for the remaining OpenControlPlane service providers

Context / Background

The topic was already partially addressed in Q2 https://github.com/openmcp-project/backlog/issues/458 providing support for the most important service providers but some still remain without support for custom CAs. We decided on tackling that proactively to close the topic instead of waiting for an actual demand.

User Stories or tasks
  • Evaluate which of the service providers require support for custom CAs
  • Implement custom CA support for the remaining service providers that need it
What is required to accept the Epic as finished.
  • All relevant components where identified (service-providers, cluster-providers, platform-services)
  • The remaining relevant components support custom CAs
Dependencies of this Epic

No response

Risks of this Epic

No response

Known Stakeholders of this Epic

No response

Milestone Definitions for this Epic.

No response

Metrics Definition for this Epic.

No response

Any further valuable resources.

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #458 and identifying the service-providers, cluster-providers, and platform-services that still lack custom CA support. Evaluate which components are relevant, then implement support for the remaining ones. Done means all relevant components are identified and the remaining relevant components support custom CAs.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.