@renchap Thanks. So the following seems to be the relevant blocking issue, correct?
https://github.com/kubermatic/kubeone/issues/2362
B
bartknubben@mastodon.nl
@bartknubben@mastodon.nl
Posts
-
Hi @MastodonEngineering and @staff, I'm on mastodon.social and would love to follow @bwb@ipv6.camp, but I can't because his instance is IPv6-only. -
Hi @MastodonEngineering and @staff, I'm on mastodon.social and would love to follow @bwb@ipv6.camp, but I can't because his instance is IPv6-only.@renchap Hi, thanks for your response. What “Kubernetes distribution” are you currently using? Thanks
-
Hi @MastodonEngineering and @staff, I'm on mastodon.social and would love to follow @bwb@ipv6.camp, but I can't because his instance is IPv6-only.@rickvanrooijen @MastodonEngineering @staff
Valid point. The mastodon.social instance already seems to support inbound IPv6: https://en.internet.nl/site/mastodon.social/3738895/#siteipv6
However, for actual interaction and federation via IPv6 outbound support is needed as well and the latter indeed seems to be missing. Hopefully they can fix this. -
@ecosia@diogop @ecosia
Agreed, I find this also disappointing. The dependency is also visible on https://hosting-checker.net/websites/ecosia.orgPlease consider switching to European options. For example, check for CDN’s: https://european-alternatives.eu/category/cdn-content-delivery-network (@european_alternatives ).