openmcp-project / openmcp-project/docs
Platform owner quickstart guide: Highlight ecosystem tooling
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 1
- Forks
- 7
- Avg merge
- 8d 9h
- Merged PRs (30d)
- 10
Description
Maybe worth highlighting here is that from this point on, it is a normal control plane. The end user interacts with it using the tools they are already used to, like kubectl, Flux, and so on. No special tooling required (ocpctl). Just the tools they already know and the familiar Kubernetes resource model. This could be a nice small selling point for those going through this guide, as they are likely the ones trying to bring it into their organization.
Originally posted by @jn-av in https://github.com/openmcp-project/docs/pull/97#discussion_r3272757896
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 with the Platform owner quickstart guide mentioned in the issue and find the section describing control-plane interaction. Update it to highlight the familiar Kubernetes resource model and ecosystem tools such as kubectl and Flux, while noting that no special ocpctl tooling is required. Done means the guide clearly presents this as a benefit for organizations adopting the platform.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100