kubermatic
Architecture diagram defaults to OpenVPN, and does not know about Konnectivity
While the presence of Konnectivity has been added to the documentation in general #913 #898, it has not been reflected in the architecture diagram at https://docs.kubermatic.com/kubermatic/v2.20/architecture/
Since Konnectivity is deemed to become the new default
https://github.com/kubermatic/docs/blob/366ab32dfe3575dd2c8869cb5b0fd224a7885fc1/content/kubermatic/master/tutorials_howtos/networking/cni_cluster_network/_index.en.md?plain=1#L98
it is suggested to
- [ ] replace OpenVPN with Konnectivity in
- https://github.com/kubermatic/docs/blob/master/static/img/kubermatic/v2.20/architecture/combined-master-seed.png
- https://github.com/kubermatic/docs/blob/master/static/img/kubermatic/v2.20/architecture/dedicated-seeds.png
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubermatic-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@embik: Reopened this issue.
In response to this:
/reopen /remove-lifecycle rotten
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale