This week we had a great listener question that went something like this:
"I work at a large company and we currently run a production Kubernetes (vendor-centric) environment. Some other groups in our company have some homegrown platforms that do similar functionality. How do we convince those other groups to work more closely with us, including potentially getting those group to switch over to our platform?"
We broke this topic down into four functional areas:
How do we rationalize having one vs multiple platforms (cost, support, feature differences)?
How do we communicate to internal groups about the capabilities of an internal platform?
How do we stop thinking like an IT group and start thinking like a product team?
In this blog post I want to introduce a nice little trick to make canary deployments possible only with Kubernetes StatefulSets and Services. First, let me give a bit of background on why I went down ...
Today, we’re making the Azure Service Operator available on OperatorHub.io to enable users to connect OpenShift clusters to Azure services, including EventHub, Azure SQL, CosmosDB, Storage Accounts, ...