KubeVirt page is not helpful or outdated regarding cluster isolation
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 19
- Forks
- 117
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 13
Description
If you are not a KKP developer, it's very hard to understand the network isolation model for KubeVirt from https://docs.kubermatic.com/kubermatic/v2.23/architecture/supported-providers/kubevirt/kubevirt.
I identified the following problems from a user perspective:
- The cluster isolation concept is not explained in a way that users are informed about it. The warning box at https://docs.kubermatic.com/kubermatic/v2.23/architecture/supported-providers/kubevirt/kubevirt/#configure-kkp-with-kubevirt is not enough since it does not explain how the cluster isolation works, nor does it give actionable examples for custom network policy configuration.
- The option to disable the cluster isolation network policies is not documented.
- I believe https://docs.kubermatic.com/kubermatic/v2.23/architecture/supported-providers/kubevirt/kubevirt/#i-created-a-load-balancer-service-on-a-user-cluster-but-services-outside-cannot-reach-it is completely out of date now and needs to be removed.
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 KubeVirt documentation page and the “Configure KKP with KubeVirt” and load-balancer sections linked in the issue. Verify the current cluster-isolation behavior and configuration options in the surrounding documentation, then update the explanation with actionable network-policy examples, document how to disable isolation, and remove the outdated load-balancer section.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100