At Container Solutions we often get asked what someone needs to do in order to be successful with microservices. This includes the technical challenges as well whether their culture and team structure is set up for success.
We who work in Cloud Native organisations have largely solved the problem of the increased complexity in setting up a Kubernetes platform. But there’s something we have not solved: how to make Kubernetes simple for developers to use.
With declarative infrastructure, what you define is what gets set up on your system. When software engineers use Helm, the package manager for Kubernetes, in building a Cloud Native system, they tend to believe that specifying a value.yaml file is being ‘declarative.’
If you’re an engineer working with containers, and especially with Kubernetes, you’re going to hear about Istio. For the uninitiated, Istio is the service mesh for Kubernetes. A service mesh is a networking layer that allows you to dynamically manage service traffic, and do so in a safe and well-defined way.
About a year ago, we at Container Solutions started our engagement with FiduciaGAD, the largest IT service provider for banks in Germany. The focus of this project is to build a Continuous Integration/Continuous Delivery platform for development teams across the organisation.