#vcluster — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #vcluster, aggregated by home.social.
-
[Перевод] Kubernetes Multitenancy в 2026 году: как мы перестали поддерживать 30 кластеров и наконец сделали все правильно
«У нас тридцать два кластера». Руководитель команды platform engineering произнес это как на исповеди. Тридцать два. В компании с девятью продуктовыми командами. По шесть окружений на каждую. Никто не планировал такого — оно просто росло по одному кластеру за раз, каждый раз, когда команде требовалось что-то чуть иное, а самым простым ответом было «подними новый». Я слышала ту или иную версию этой фразы почти в каждой компании, достигшей определенного размера. Цифра меняется — иногда двенадцать, иногда шестьдесят, — но динамика всегда одна. Kubernetes легко позволяет создавать кластеры, никто намеренно не решал, когда их использовать совместно, а когда нет, и в какой-то момент кто-то смотрит на счет за облако и ротацию дежурств — и понимает, что управление десятками кластеров медленно пожирает платформенную команду заживо. Multitenancy — ответ на эту проблему. Kubernetes не был спроектирован для multitenancy из коробки, и, чтобы построить его правильно, требуются реальные инженерные инвестиции, но именно так зрелые команды platform engineering решают эту задачу в 2026 году — со все более удобным инструментарием и все лучше понятыми паттернами. Команда VK Cloud перевела статью, охватывающую все, что автор узнал о Kubernetes multitenancy в нескольких продакшен-окружениях: какие модели существуют, где каждая из них дает сбой, как выстроить слои изоляции, которые действительно защищают тенантов друг от друга, какие инструменты стоят вашего времени и как выглядит хорошо управляемый общий кластер на практике. Если ваша команда управляет слишком большим количеством кластеров или строит платформу для безопасного обслуживания нескольких команд — это руководство, которого мне так не хватало в начале пути.
https://habr.com/ru/companies/vktech/articles/1054016/
#vk_cloud #kubernetes #multitenancy #networkpolicy #vcluster #capsule #kyverno #finops #platformengineering #resourcequota
-
[Перевод] Kubernetes Multitenancy в 2026 году: как мы перестали поддерживать 30 кластеров и наконец сделали все правильно
«У нас тридцать два кластера». Руководитель команды platform engineering произнес это как на исповеди. Тридцать два. В компании с девятью продуктовыми командами. По шесть окружений на каждую. Никто не планировал такого — оно просто росло по одному кластеру за раз, каждый раз, когда команде требовалось что-то чуть иное, а самым простым ответом было «подними новый». Я слышала ту или иную версию этой фразы почти в каждой компании, достигшей определенного размера. Цифра меняется — иногда двенадцать, иногда шестьдесят, — но динамика всегда одна. Kubernetes легко позволяет создавать кластеры, никто намеренно не решал, когда их использовать совместно, а когда нет, и в какой-то момент кто-то смотрит на счет за облако и ротацию дежурств — и понимает, что управление десятками кластеров медленно пожирает платформенную команду заживо. Multitenancy — ответ на эту проблему. Kubernetes не был спроектирован для multitenancy из коробки, и, чтобы построить его правильно, требуются реальные инженерные инвестиции, но именно так зрелые команды platform engineering решают эту задачу в 2026 году — со все более удобным инструментарием и все лучше понятыми паттернами. Команда VK Cloud перевела статью, охватывающую все, что автор узнал о Kubernetes multitenancy в нескольких продакшен-окружениях: какие модели существуют, где каждая из них дает сбой, как выстроить слои изоляции, которые действительно защищают тенантов друг от друга, какие инструменты стоят вашего времени и как выглядит хорошо управляемый общий кластер на практике. Если ваша команда управляет слишком большим количеством кластеров или строит платформу для безопасного обслуживания нескольких команд — это руководство, которого мне так не хватало в начале пути.
https://habr.com/ru/companies/vktech/articles/1054016/
#vk_cloud #kubernetes #multitenancy #networkpolicy #vcluster #capsule #kyverno #finops #platformengineering #resourcequota
-
[Перевод] Kubernetes Multitenancy в 2026 году: как мы перестали поддерживать 30 кластеров и наконец сделали все правильно
«У нас тридцать два кластера». Руководитель команды platform engineering произнес это как на исповеди. Тридцать два. В компании с девятью продуктовыми командами. По шесть окружений на каждую. Никто не планировал такого — оно просто росло по одному кластеру за раз, каждый раз, когда команде требовалось что-то чуть иное, а самым простым ответом было «подними новый». Я слышала ту или иную версию этой фразы почти в каждой компании, достигшей определенного размера. Цифра меняется — иногда двенадцать, иногда шестьдесят, — но динамика всегда одна. Kubernetes легко позволяет создавать кластеры, никто намеренно не решал, когда их использовать совместно, а когда нет, и в какой-то момент кто-то смотрит на счет за облако и ротацию дежурств — и понимает, что управление десятками кластеров медленно пожирает платформенную команду заживо. Multitenancy — ответ на эту проблему. Kubernetes не был спроектирован для multitenancy из коробки, и, чтобы построить его правильно, требуются реальные инженерные инвестиции, но именно так зрелые команды platform engineering решают эту задачу в 2026 году — со все более удобным инструментарием и все лучше понятыми паттернами. Команда VK Cloud перевела статью, охватывающую все, что автор узнал о Kubernetes multitenancy в нескольких продакшен-окружениях: какие модели существуют, где каждая из них дает сбой, как выстроить слои изоляции, которые действительно защищают тенантов друг от друга, какие инструменты стоят вашего времени и как выглядит хорошо управляемый общий кластер на практике. Если ваша команда управляет слишком большим количеством кластеров или строит платформу для безопасного обслуживания нескольких команд — это руководство, которого мне так не хватало в начале пути.
https://habr.com/ru/companies/vktech/articles/1054016/
#vk_cloud #kubernetes #multitenancy #networkpolicy #vcluster #capsule #kyverno #finops #platformengineering #resourcequota
-
Friends don't let friends run production etcd on SATA disks (or basically anywhere other than local NVMe)!
I was deploying 50 kubernetes virtual clusters (with vcluster) on top of a bare metal cluster running Talos.
All the nodes had NVMe disks, except one, which had SATA SSD... And it did not go well at all.
I was expecting to see a difference, but not that big. The SATA disks were saturated while the NVMe were hovering between 1-5% of I/O load.
The SATA disks were so overloaded, that I had to kick out their node from the etcd cluster (because the API server was extremely slow).
Oh well, it'll be 100% NVMe on this cluster from now on!
-
Friends don't let friends run production etcd on SATA disks (or basically anywhere other than local NVMe)!
I was deploying 50 kubernetes virtual clusters (with vcluster) on top of a bare metal cluster running Talos.
All the nodes had NVMe disks, except one, which had SATA SSD... And it did not go well at all.
I was expecting to see a difference, but not that big. The SATA disks were saturated while the NVMe were hovering between 1-5% of I/O load.
The SATA disks were so overloaded, that I had to kick out their node from the etcd cluster (because the API server was extremely slow).
Oh well, it'll be 100% NVMe on this cluster from now on!
-
Friends don't let friends run production etcd on SATA disks (or basically anywhere other than local NVMe)!
I was deploying 50 kubernetes virtual clusters (with vcluster) on top of a bare metal cluster running Talos.
All the nodes had NVMe disks, except one, which had SATA SSD... And it did not go well at all.
I was expecting to see a difference, but not that big. The SATA disks were saturated while the NVMe were hovering between 1-5% of I/O load.
The SATA disks were so overloaded, that I had to kick out their node from the etcd cluster (because the API server was extremely slow).
Oh well, it'll be 100% NVMe on this cluster from now on!
-
Friends don't let friends run production etcd on SATA disks (or basically anywhere other than local NVMe)!
I was deploying 50 kubernetes virtual clusters (with vcluster) on top of a bare metal cluster running Talos.
All the nodes had NVMe disks, except one, which had SATA SSD... And it did not go well at all.
I was expecting to see a difference, but not that big. The SATA disks were saturated while the NVMe were hovering between 1-5% of I/O load.
The SATA disks were so overloaded, that I had to kick out their node from the etcd cluster (because the API server was extremely slow).
Oh well, it'll be 100% NVMe on this cluster from now on!
-
Friends don't let friends run production etcd on SATA disks (or basically anywhere other than local NVMe)!
I was deploying 50 kubernetes virtual clusters (with vcluster) on top of a bare metal cluster running Talos.
All the nodes had NVMe disks, except one, which had SATA SSD... And it did not go well at all.
I was expecting to see a difference, but not that big. The SATA disks were saturated while the NVMe were hovering between 1-5% of I/O load.
The SATA disks were so overloaded, that I had to kick out their node from the etcd cluster (because the API server was extremely slow).
Oh well, it'll be 100% NVMe on this cluster from now on!
-
AI-generated #Kubernetes YAML looks perfect — until you apply it.
Hallucinated fields. Wrong versions. Deprecated options.
All symptoms of pattern-matching without grounding in real schema.
So I built a fun experiment: first a #vCluster YAML CLI to help me validate my own configs. Then I thought: why not package it as an MCP server and let AI do it?
The results were surprisingly good!
Try it yourself: https://piotrzan.medium.com/stop-ai-from-hallucinating-your-kubernetes-yaml-10142f685a8b
-
AI-generated #Kubernetes YAML looks perfect — until you apply it.
Hallucinated fields. Wrong versions. Deprecated options.
All symptoms of pattern-matching without grounding in real schema.
So I built a fun experiment: first a #vCluster YAML CLI to help me validate my own configs. Then I thought: why not package it as an MCP server and let AI do it?
The results were surprisingly good!
Try it yourself: https://piotrzan.medium.com/stop-ai-from-hallucinating-your-kubernetes-yaml-10142f685a8b
-
AI-generated #Kubernetes YAML looks perfect — until you apply it.
Hallucinated fields. Wrong versions. Deprecated options.
All symptoms of pattern-matching without grounding in real schema.
So I built a fun experiment: first a #vCluster YAML CLI to help me validate my own configs. Then I thought: why not package it as an MCP server and let AI do it?
The results were surprisingly good!
Try it yourself: https://piotrzan.medium.com/stop-ai-from-hallucinating-your-kubernetes-yaml-10142f685a8b
-
#vcluster and multitenancy stream just started: https://www.youtube.com/watch?v=il5sYzSoHP4
-
#vcluster and multitenancy stream just started: https://www.youtube.com/watch?v=il5sYzSoHP4
-
#vcluster and multitenancy stream just started: https://www.youtube.com/watch?v=il5sYzSoHP4
-
Even More #OpenTelemetry - #Kubernetes special.
* From Docker Compose to #Helm
* Helm subcharts for the win
* Kubernetes topology with #vCluster
* #Traefik as an Ingress Controller
* Exposing services and the Ingress class
* A touch of the #OpenTelemetryCollector
* Initializing PostgreSQL with data
* Kubernetes instrumentation of pods
* Bonus: A new #Quarkus component -
Even More #OpenTelemetry - #Kubernetes special.
* From Docker Compose to #Helm
* Helm subcharts for the win
* Kubernetes topology with #vCluster
* #Traefik as an Ingress Controller
* Exposing services and the Ingress class
* A touch of the #OpenTelemetryCollector
* Initializing PostgreSQL with data
* Kubernetes instrumentation of pods
* Bonus: A new #Quarkus component -
Even More #OpenTelemetry - #Kubernetes special.
* From Docker Compose to #Helm
* Helm subcharts for the win
* Kubernetes topology with #vCluster
* #Traefik as an Ingress Controller
* Exposing services and the Ingress class
* A touch of the #OpenTelemetryCollector
* Initializing PostgreSQL with data
* Kubernetes instrumentation of pods
* Bonus: A new #Quarkus component -
Even More #OpenTelemetry - #Kubernetes special.
* From Docker Compose to #Helm
* Helm subcharts for the win
* Kubernetes topology with #vCluster
* #Traefik as an Ingress Controller
* Exposing services and the Ingress class
* A touch of the #OpenTelemetryCollector
* Initializing PostgreSQL with data
* Kubernetes instrumentation of pods
* Bonus: A new #Quarkus component -
Even More #OpenTelemetry - #Kubernetes special.
* From Docker Compose to #Helm
* Helm subcharts for the win
* Kubernetes topology with #vCluster
* #Traefik as an Ingress Controller
* Exposing services and the Ingress class
* A touch of the #OpenTelemetryCollector
* Initializing PostgreSQL with data
* Kubernetes instrumentation of pods
* Bonus: A new #Quarkus component -
Solve the multi-tenancy problem in Kubernetes and reduce costs at the same time? 🤔 Virtual clusters – aka vClusters – have their own API server and are therefore more powerful and better isolated than namespaces. 🚀🏝️ But that's not all: they are also much cheaper than real Kubernetes clusters. 💰 You can find all further details about our vCluster offer here https://nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine
-
Solve the multi-tenancy problem in Kubernetes and reduce costs at the same time? 🤔 Virtual clusters – aka vClusters – have their own API server and are therefore more powerful and better isolated than namespaces. 🚀🏝️ But that's not all: they are also much cheaper than real Kubernetes clusters. 💰 You can find all further details about our vCluster offer here https://nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine
-
Solve the multi-tenancy problem in Kubernetes and reduce costs at the same time? 🤔 Virtual clusters – aka vClusters – have their own API server and are therefore more powerful and better isolated than namespaces. 🚀🏝️ But that's not all: they are also much cheaper than real Kubernetes clusters. 💰 You can find all further details about our vCluster offer here https://nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine
-
Solve the multi-tenancy problem in Kubernetes and reduce costs at the same time? 🤔 Virtual clusters – aka vClusters – have their own API server and are therefore more powerful and better isolated than namespaces. 🚀🏝️ But that's not all: they are also much cheaper than real Kubernetes clusters. 💰 You can find all further details about our vCluster offer here https://nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine
-
This week’s post is the third and final in my series about running tests on #Kubernetes for each pull request. In the 1st post, I described the app and how to test locally using #Testcontainers and in a #GitHub workflow. The second post focused on setting up #GKE and running end-to-end tests on Kubernetes.
In this post, I’ll show how to benefit from the best of both worlds with #vCluster: a single cluster with testing from each PR in complete isolation from others.
-
This week’s post is the third and final in my series about running tests on #Kubernetes for each pull request. In the 1st post, I described the app and how to test locally using #Testcontainers and in a #GitHub workflow. The second post focused on setting up #GKE and running end-to-end tests on Kubernetes.
In this post, I’ll show how to benefit from the best of both worlds with #vCluster: a single cluster with testing from each PR in complete isolation from others.
-
This week’s post is the third and final in my series about running tests on #Kubernetes for each pull request. In the 1st post, I described the app and how to test locally using #Testcontainers and in a #GitHub workflow. The second post focused on setting up #GKE and running end-to-end tests on Kubernetes.
In this post, I’ll show how to benefit from the best of both worlds with #vCluster: a single cluster with testing from each PR in complete isolation from others.
-
This week’s post is the third and final in my series about running tests on #Kubernetes for each pull request. In the 1st post, I described the app and how to test locally using #Testcontainers and in a #GitHub workflow. The second post focused on setting up #GKE and running end-to-end tests on Kubernetes.
In this post, I’ll show how to benefit from the best of both worlds with #vCluster: a single cluster with testing from each PR in complete isolation from others.
-
This week’s post is the third and final in my series about running tests on #Kubernetes for each pull request. In the 1st post, I described the app and how to test locally using #Testcontainers and in a #GitHub workflow. The second post focused on setting up #GKE and running end-to-end tests on Kubernetes.
In this post, I’ll show how to benefit from the best of both worlds with #vCluster: a single cluster with testing from each PR in complete isolation from others.
-
How to Build a #Multitenancy Internal Developer Platform (#IDP) with #GitOps and #vCluster
-
How to Build a #Multitenancy Internal Developer Platform (#IDP) with #GitOps and #vCluster
-
How to Build a #Multitenancy Internal Developer Platform (#IDP) with #GitOps and #vCluster
-
How to Build a #Multitenancy Internal Developer Platform (#IDP) with #GitOps and #vCluster
-
How to Build a #Multitenancy Internal Developer Platform (#IDP) with #GitOps and #vCluster
-
Thanks @BeJUG 🇧🇪 for having me and thanks @TCoolsIT for the organization.
I'm happy to have explained to developers how to use @opentelemetry with a touch of #vcluster.
-
Thanks @BeJUG 🇧🇪 for having me and thanks @TCoolsIT for the organization.
I'm happy to have explained to developers how to use @opentelemetry with a touch of #vcluster.
-
Thanks @BeJUG 🇧🇪 for having me and thanks @TCoolsIT for the organization.
I'm happy to have explained to developers how to use @opentelemetry with a touch of #vcluster.
-
Thanks @BeJUG 🇧🇪 for having me and thanks @TCoolsIT for the organization.
I'm happy to have explained to developers how to use @opentelemetry with a touch of #vcluster.
-
Thanks @BeJUG 🇧🇪 for having me and thanks @TCoolsIT for the organization.
I'm happy to have explained to developers how to use @opentelemetry with a touch of #vcluster.
-
I finished today my demo about #WebAssembly on @kubernetesio with a touch of #vCluster.
I'll be ready for my talk JCon conference in Köln on May 13th. Interested? Join me there 😎
-
I finished today my demo about #WebAssembly on @kubernetesio with a touch of #vCluster.
I'll be ready for my talk JCon conference in Köln on May 13th. Interested? Join me there 😎
-
I finished today my demo about #WebAssembly on @kubernetesio with a touch of #vCluster.
I'll be ready for my talk JCon conference in Köln on May 13th. Interested? Join me there 😎
-
I finished today my demo about #WebAssembly on @kubernetesio with a touch of #vCluster.
I'll be ready for my talk JCon conference in Köln on May 13th. Interested? Join me there 😎
-
I finished today my demo about #WebAssembly on @kubernetesio with a touch of #vCluster.
I'll be ready for my talk JCon conference in Köln on May 13th. Interested? Join me there 😎
-
#ChaosEngineering with #ChaosMesh and #vCluster: Testing Close to Production
-
#ChaosEngineering with #ChaosMesh and #vCluster: Testing Close to Production
-
#ChaosEngineering with #ChaosMesh and #vCluster: Testing Close to Production
-
#ChaosEngineering with #ChaosMesh and #vCluster: Testing Close to Production
-
#ChaosEngineering with #ChaosMesh and #vCluster: Testing Close to Production
-
Put your #Kubernetes workloads to sleep using #vCluster native sleep mode
-
Put your #Kubernetes workloads to sleep using #vCluster native sleep mode
-
Put your #Kubernetes workloads to sleep using #vCluster native sleep mode
-
Put your #Kubernetes workloads to sleep using #vCluster native sleep mode
-
Put your #Kubernetes workloads to sleep using #vCluster native sleep mode
-
I’m an average Reddit user, scrolling much more than reading or interacting. Sometimes, however, a post rings a giant red bell. When I stumbled upon If you could add one feature to #Kubernetes, what would it be?, I knew the content would be worth it. The most voted answer is:
Namespace scoped #CRDs
Here's a solution with #vCluster
-
I’m an average Reddit user, scrolling much more than reading or interacting. Sometimes, however, a post rings a giant red bell. When I stumbled upon If you could add one feature to #Kubernetes, what would it be?, I knew the content would be worth it. The most voted answer is:
Namespace scoped #CRDs
Here's a solution with #vCluster