Tag Archives: Vendors

Successful Vendoring in Open Source

How can we make Open Source go faster, and how can we improve its interaction with vendors, especially hardware vendors?

We explore different ways that open source helps foster innovation, as well as where it creates ethical, financial, and legal conflicts in that process.

Thinking through how we want to bring vendor information into Open Source communities is an ongoing challenge.

Transcript: otter.ai/u/gTvOzZXkvWfYPOkVSvkAbJRrIB4
Image: www.pexels.com/photo/closed-blue…den-doors-350626/

Rob’s Hot Take:

In the June 7th episode, Rob Hirschfeld addresses the challenging aspect of establishing vendor areas for innovation within open-source communities. Striking a balance is crucial as vendors must avoid being too pushy with vendor-specific elements that undermine the open-source commons. Effective open-source communities find a middle ground, enabling vendors to contribute, extend, or replace components without compromising the integrity of the community. For a deeper exploration of this topic, listen to the full conversation at the2030.cloud, and join the ongoing discussions.

Can Kubernetes Prevent Vendor Lock In?

How does Kubernetes create lock in versus how could Kubernetes be used to prevent lock in?

Lock in is not always a bad thing. When you avoid committing to a single vendor, you may have to work to the lowest common denominator or deal with heterogeneity in your infrastructure. Heterogeneity is pretty normal, and you might have to do this work regardless, but when you commit to a vendor you get to focus on using the vendor’s strengths.

In this episode, you’ll pick up some great tips on how to reduce your lock in when using Kubernetes.

Transcript: otter.ai/u/vIo1p15bb6VmcrWjwgOLbM25nq4
Image: www.pexels.com/photo/silhouette-…door-knob-792032/

Rob’s Hot Take:

In the April 12th episode of the Cloud 2030 Podcast, Rob Hirschfeld delves into the nuanced discussion of whether Kubernetes prevents or exacerbates vendor lock-in. The key takeaway is that lock-in is not inherently negative, and there’s a need to balance risks and consider the inertia associated with established systems and practices. The podcast encourages listeners to think intentionally about using Kubernetes as an abstraction layer and to recognize the value and challenges of inertia in platform development efforts. For further insights and discussions on DevOps and future strategies, visit the2030.cloud and join the conversation.