home.social

#vcluster — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vcluster, aggregated by home.social.

  1. #vCluster (my new gig) is doing some really interesting work in the Kubernetes and infrastructure space. It's great people, an interesting product suite, and a set of challenges that pique the curiosity.

    If that sounds like something you're interested in, there's lots of roles open from technical account managers, support, product, customer success, and marketing.

    We make heavy use of LLMs. So if that's a no for you, then this isn't the link to follow.

    vcluster.com/careers#jobs

    This is a post about connecting people to jobs in a challenging market for that. If you feel the need to comment about AI, please don't.

    #getFediHired

  2. #vCluster (my new gig) is doing some really interesting work in the Kubernetes and infrastructure space. It's great people, an interesting product suite, and a set of challenges that pique the curiosity.

    If that sounds like something you're interested in, there's lots of roles open from technical account managers, support, product, customer success, and marketing.

    We make heavy use of LLMs. So if that's a no for you, then this isn't the link to follow.

    vcluster.com/careers#jobs

    This is a post about connecting people to jobs in a challenging market for that. If you feel the need to comment about AI, please don't.

    #getFediHired

  3. #vCluster (my new gig) is doing some really interesting work in the Kubernetes and infrastructure space. It's great people, an interesting product suite, and a set of challenges that pique the curiosity.

    If that sounds like something you're interested in, there's lots of roles open from technical account managers, support, product, customer success, and marketing.

    We make heavy use of LLMs. So if that's a no for you, then this isn't the link to follow.

    vcluster.com/careers#jobs

    This is a post about connecting people to jobs in a challenging market for that. If you feel the need to comment about AI, please don't.

    #getFediHired

  4. #vCluster (my new gig) is doing some really interesting work in the Kubernetes and infrastructure space. It's great people, an interesting product suite, and a set of challenges that pique the curiosity.

    If that sounds like something you're interested in, there's lots of roles open from technical account managers, support, product, customer success, and marketing.

    We make heavy use of LLMs. So if that's a no for you, then this isn't the link to follow.

    vcluster.com/careers#jobs

    This is a post about connecting people to jobs in a challenging market for that. If you feel the need to comment about AI, please don't.

    #getFediHired

  5. #vCluster (my new gig) is doing some really interesting work in the Kubernetes and infrastructure space. It's great people, an interesting product suite, and a set of challenges that pique the curiosity.

    If that sounds like something you're interested in, there's lots of roles open from technical account managers, support, product, customer success, and marketing.

    We make heavy use of LLMs. So if that's a no for you, then this isn't the link to follow.

    vcluster.com/careers#jobs

    This is a post about connecting people to jobs in a challenging market for that. If you feel the need to comment about AI, please don't.

    #getFediHired

  6. Successful first day!

    #vCluster is doing some really, really interesting things in the Kubernetes space!

  7. Successful first day!

    #vCluster is doing some really, really interesting things in the Kubernetes space!

  8. Successful first day!

    #vCluster is doing some really, really interesting things in the Kubernetes space!

  9. Successful first day!

    #vCluster is doing some really, really interesting things in the Kubernetes space!

  10. Successful first day!

    #vCluster is doing some really, really interesting things in the Kubernetes space!

  11. AI-generated 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 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: piotrzan.medium.com/stop-ai-fr

  12. 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: piotrzan.medium.com/stop-ai-fr

  13. 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: piotrzan.medium.com/stop-ai-fr

  14. 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

    blog.frankel.ch/even-more-open

  15. 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

    blog.frankel.ch/even-more-open

  16. 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

    blog.frankel.ch/even-more-open

  17. 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

    blog.frankel.ch/even-more-open

  18. 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

    blog.frankel.ch/even-more-open

  19. 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 nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine

  20. 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 nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine

  21. 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 nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine

  22. 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 nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine

  23. 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.

    blog.frankel.ch/pr-testing-kub

  24. 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.

    blog.frankel.ch/pr-testing-kub

  25. 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.

    blog.frankel.ch/pr-testing-kub

  26. 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.

    blog.frankel.ch/pr-testing-kub

  27. 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.

    blog.frankel.ch/pr-testing-kub

  28. 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.

  29. 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.

  30. 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.

  31. 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.

  32. 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.

  33. 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 😎

    schedule.jcon.one/session/7839

  34. 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 😎

    schedule.jcon.one/session/7839

  35. 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 😎

    schedule.jcon.one/session/7839

  36. 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 😎

    schedule.jcon.one/session/7839

  37. 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 😎

    schedule.jcon.one/session/7839