Kubernetes isn't something that you just "turn on" and walk away.
It's a platform that has to be considered a main part of how you deploy.
But how?
A thread ๐งต
It's a platform that has to be considered a main part of how you deploy.
But how?
A thread ๐งต
It should be looked at no different than when you began to implement VMWare on bare metal or the cloud in your environment.
Kubernetes can't be something that's just on the back burner and implemented with 10% capacity. You have to think about:
Kubernetes can't be something that's just on the back burner and implemented with 10% capacity. You have to think about:
โ
What the future of the environment will look like
โ How you'll plan upgrades
โ What your backup and disaster recovery plan is
โ How you're going to move platforms/environments (for example - AWS to Azure) if you need to
โ How you'll plan upgrades
โ What your backup and disaster recovery plan is
โ How you're going to move platforms/environments (for example - AWS to Azure) if you need to
A lot of the time, I see Kubernetes almost looked at as some type of application. You just "install it" and if it doesn't work, you walk away.
It has to be looked at as a primary part of your entire environment. Otherwise, the overall implementation will fail.
#kubernetes
It has to be looked at as a primary part of your entire environment. Otherwise, the overall implementation will fail.
#kubernetes
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
ใ
