Outdated doc: "Working with vRack example - Communicating between different private networks"
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 273
- Forks
- 391
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Hey
This page seems outdated when reading it: https://help.ovhcloud.com/csm/fr-public-cloud-kubernetes-vrack-example-between-private-networks?id=kb_article_view&sysparm_article=KB0055408
It helpfully states:
The method described in this tutorial is a temporary one, only required if you want to route traffic between different private networks in a single vRack. Our Managed Kubernetes team is working on a more streamlined solution for this advanced use case, as explained in this issue in our Public Cloud roadmap.
That issue has been closed in 22H2: https://github.com/ovh/public-cloud-roadmap/issues/116#issuecomment-1195589940
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
Open the linked OVHcloud help page and review roadmap issue 116 and its closing comment to confirm which guidance is obsolete. Locate the corresponding page in this repository, update the outdated vRack statement using the current guidance available there, and verify the rendered documentation no longer presents the closed roadmap work as pending.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100