UpskillingKubernetes

I'd say lift and shift is still the main road, try to go in MVP cycles, try, fail, repeat https://www.devopsgroup.com/blog/simplifying-optio...

Not to go into a big bang, project driven transformation but to try to decouple through small, continuous experiments and look to patterns like strangler

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.

Ignores on-prem, integrations and polishing CD/CI architecture

Vendor lockin?

I like that vendor locking advise.

Keeping Kubernetes only a part of Infrastructure and not the the entire DevOps Culture Transformation exercise!

Kubernetes is the#1 container orchestration solution because it is free open source and does a great job of automating most of container orchestration use cases.

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

i would say "Feel the Rhythm feel the rhyme get on up its Kubernetes time"

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 process
b. Interacts with several groups of containers
c. Self-monitoring
d. Horizontal scaling
e. Storage orchestration
f. Automates rollouts and rollback
g. Container balancing

Self healing

Nice list! We'll get more into the advantages in a bit!

Auto Scaling

We see a paradigm shift with devops using kubernetes and being an open source, it is gaining more traction

Let's have in mind that it's great to auto scale up, auto scaling down is still a hard one to do and very dependant on the application itself

Self healing is game changer

@anuragthoughts Sel healing is the way to #NoOps

Self healing*

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

(edited)

managing cluster operation

Great one @mhexcalibur I would also say infrastructure as code is essential, and knowing your containers inside out :)

Cloud skills, Build and release skills, Coding and scripting, security and compliance understanding

Cloud Computing skills are essential

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

#SRE skills are getting hot day by day and they complement to #kubernetes

Agree - but I think basic understandings of microservices, containers and Kubernetes is needed. @tracyragan

SRE and Service management must it helps a lot

@anuragthoughts I completely agree. Passionate about #ITSM and #SRE

I love this site for learning about microservices https://microservices.io/

@TracyRagan And then if you are new to Kubernetes https://www.youtube.com/watch?v=R9-SOzep73w

Resistance, Lack of skills, Lack of Training, Lack of Management on assigning resources to the work

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

Like Mark - thinking they are some sort of panacea and not considering all the other things that DevOps teaches us about trust, transparency, learning, courage and curiosity

most of org still in transformation journey lack of skill and value awareness creates resistance from management

Fundamental understanding on who can work on Container related work! There is thin line while considering DevOps skills and DevOps engineers are given every work and that results into resistance!

right, the main problem are related with the devops model. Most of top executives do not understand what or why devops

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.

(edited)

1. Start by Targeting the Right Kind of Application
2. Consider Team and Human Capabilities
3. Adopt Pure Open-Source Kubernetes
4. Work Out The Enterprise Integrations
5. Stay Conversant with Kubernetes Changes
6. Incrementally Iterate

12 factor apps https://12factor.net/

Always consider team capability, try to invest in SREs,
Remain cloud neutral use pure Kubernetes, vanilla
Start with right application and have patience

3 musketeers https://3musketeers.io/

To utilize Cloud based Kubernetes services such as AKS

Greatly important. Going back to devops 2nd way, Feedback is critical and you need observability and monitoring to measure progress along the value chain and deployment pipeline

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

Right

It's crucial to have business drive metrics to see how much we are achieving with our DevOps strategy.

We have now termed it as BUSDEVOPS