That all of this (K8s and microservices) can be managed by scripts using a few smart people. Automation and tooling is required. Home grown solutions will only work initially but will not sustain in the long run.

Kubernetes simply offers a frontier for software development. new DevOps phase going to programmatic, elastic, and declarative where k8s can helps organizations run containers at the edge such that there is a maximization of resources, smoother and faster functioning

Kubernetes is definitely becoming more and more prominent, the same way cloud did in the past, as a way to be able to deliver orchestrated self-healing platforms that can grow with demand, and it's free!

There are several advantages of #Kubernetes a. Automates various manual processb. Interacts with several groups of containersc. Self-monitoringd. Horizontal scalinge. Storage orchestrationf. Automates rollouts and rollbackg. Container balancing

I recommend this article: https://blog.digitalocean.com/closing-the-kubernet... which emphasizes the following skills:○ Learning Kubernetes core concepts○ Modernizing applications to work with containers○ Containerizing applications○ Deploying applications to Kubernetes○ Managing c

Closing the Kubernetes Skills Gap with Developer-First LearningHow do you begin learning Kubernetes? This is an important question for any organization building, hosting, or managing applications today. For DigitalOcean, which released its managed Kubernetes product in 2018, it's essential. The demand for develo...

That depends on what side you are on Dev or Ops. On the Ops side, understanding how Kubernetes enhances VM (the underlying tech) you will begin to see why you should make the move. On the Dev side, you need to start seeing a 'Cluster' as what you are building out. Microservice

What are microservices?Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities. The microservice architecture enables the conti...

Cultural issues are not with containers, but with the DevOps model. Someone mentioned the other day, Containers become cargo cult --- C-suite thinks employing containers should solve all other dev issues

Businesses not understanding what are the advantages of containers and hydra style applications (highly resilient) and trying to reimplement their datacenter in K8s, round peg for square hole kind of approach

Docker is easy, so it makes containers easy - but to build out a complete platform is hard. Developers must understand the wider view. Ops need to see why developers want to make the jump. There is a disconnect between the two.

1) Approach this from a Domain Driven Design - 2) Understand how development is disrupted - 3) Take it slow and start by containerizing apps running in K8s 4) Decompose applications that benefit from a k8s architecture.

1. Start by Targeting the Right Kind of Application2. Consider Team and Human Capabilities3. Adopt Pure Open-Source Kubernetes4. Work Out The Enterprise Integrations5. Stay Conversant with Kubernetes Changes6. Incrementally Iterate

For me observability is the icing on the cake as SRE is the icing on top of modern infrastructure, be able to trace your events from beginning to end is essential as systems are getting more complex and micro-fragmented