Kubernetes Expert Interviews: Adopting K8s as a Team
Accelerating the Kubernetes Journey for Cloud Native Organizations
Perspectives on the platforms, paved paths, and developer experience for organizations adopting Kubernetes
Learn from Ambassador Experts
- Use Your Own Tools: An Ambassador Engineering Manager's View
- Use Your Own Tools: An Ambassador VP of Engineering's View (coming soon!)
- Use Your Own Tools: A Principal Engineer's Perspective (coming soon!)
- And more will be published soon!
Read the Thought Leadership Interviews
Platform builders, Kubernetes developers, and tech leaders share their insights
Many companies are building a platform, “paved path,” or developer control plane on top of Kubernetes. The teams responsible for building these platforms have many names, from platform engineering to DevOps, from site reliability engineer (SRE) to developer experience (DX) teams, but they all have one goal: reduce the friction and toil for developers coding, shipping, and running their applications.
This has fundamentally changed the developer experience, creating a need for closer collaboration and demanding a centralized path for developers to be able to create, deliver, and run apps with speed and safety.
In these guides, experts and leaders in the cloud native space share their take on the importance of technologies, education, culture, and community for the goal of achieving cloud native maturity. SRE and platform teams, developers, and leaders also share some common perspectives about how developer control planes like Ambassador Cloud have helped ease the transition.
Download our free guides today!
Transforming Developer Productivity with Kubernetes
Learn how you can boost the cloud native developer experience for your team.
Preparing Cloud-Native Businesses for Long-term Success
Learn the key concepts to leverage on your team's journey to Kubernetes maturity.
Learn from the experts
Platform Engineering in 2022: Onramps, Self-Service, and Standardization
Developer Control Planes: An Experienced SRE's Point of View
The Developer Experience and the Role of the SRE Are Changing, Here's How
Developer Control Planes: A Platform Architect's Point of View
Lessons from the K8s Vanguard: Invest in Onboarding, Freedom & Responsibility, and Integrated Tooling
Developer Control Planes: A (Google) Developer's Point of View
From Dev to Ops: Infrastructure is Hard, but Tooling and Visibility are the Key for Full Cycle Developers
Developer Control Planes: An Engineering Leadership Point of View
A Leadership View on Cloud-Native Development: Focus on Uptime, Collaboration, and Developer Self-Service
Developer Control Planes: A CTO's Point of View
Making Sense of the Chaos: Considerations for a Cloud-Native Future
Developer Control Planes: An Ecosystem Leader’s Point of View
It's all about the community: "Technology is good, but the cloud-native community is what really makes it great"
Developer Control Planes: A Cloud Leader's Point of View
Empathy, Security, and Developer Experience: The Next Steps in the Cloud Maturity Curve
Developer Control Planes: A Platform Builder's Point of View
Building the Business Case for a Developer Control Plane
Developer Control Planes: A Platform Engineer's Point of View
Designing Platforms: Wrangling Complexity for a Better Developer Experience
Developer Control Planes: An Engineering Director's Point of View
Platform Engineering, Adopting Team Topologies, and Supporting the Developer Experience
Developer Control Planes: A Community Practice Engineer's Point of View
Communities of Practice, Improving the Software Engineering Craft and Developer Control Planes
HTTP/3: Use Cases, Envoy Support, and Google’s Rollout
Defining Goals and Developer Responsibilities in the Cloud-Native Journey
How Internal Developer Advocacy Leads to Improved DevEx
Supercharge your productivity by adopting full-service ownership:
SRE, Platform, and Operational Teams
Create ideal conditions for safely shipping software faster:
Champion the end-to-end “developer as service owner” mindset:
"The Developer Control Plane frees us to utilize the power of our cluster while also keeping the cluster really small. Each of us can work concurrently using resources working off the same dataset, allowing us to maximize efficiency. It also frees us up to work on wildly different development setups based on personal preference.” - Dave Sudia, CTO at Upchieve