Re:Deckhouse: NoOps Kubernetes platform
by bradhe on Tuesday August 03, 2021 @11:04AM
(#28050051)
Yeah but people read "No Ops" as "you don't need to do operations" not "you don't need to hire operations." You can try to fight that fight if you want but I think it's already come and gone.
Re:Deckhouse: NoOps Kubernetes platform
by xfitm3 on Tuesday August 03, 2021 @09:56AM
(#28049226)
I think this is a conflict of interest, ultimately. There should be separation of duties. You need guardrails in place, and you have to hire to manage these guardrails.
In my experience development members know enough to be dangerous, and this can lead to misconfigurations / potential security incidents.
Re:Deckhouse: NoOps Kubernetes platform
by shurup on Wednesday August 04, 2021 @06:02AM
(#28059190)
First of all, that's kinda apples and oranges. If kops is basically an installer, Deckhouse is much more a Kubernetes distribution. It's not just about deploying new clusters but about keeping them running all the way.
Kops installs a "bare" cluster; Deckhouse gives you a set of integrated modules for monitoring, authentication, etc. — as much "out of the box" as you might need to run real applications in K8s. Another outcome is that when you upgrade the Kubernetes version in Deckhouse, it also makes all the relevant work with components and modules in use (they are also updated with compatibility issues in mind, thus everything "just works"). That's why it's marketed as NoOps: it aspires to automate all these routine operations [so you can focus on other exciting challenges ;)].
Deckhouse can also be installed on bare-metal servers, provides SLAs & support for those who need.
In my experience development members know enough to be dangerous, and this can lead to misconfigurations / potential security incidents.
Kops installs a "bare" cluster; Deckhouse gives you a set of integrated modules for monitoring, authentication, etc. — as much "out of the box" as you might need to run real applications in K8s. Another outcome is that when you upgrade the Kubernetes version in Deckhouse, it also makes all the relevant work with components and modules in use (they are also updated with compatibility issues in mind, thus everything "just works"). That's why it's marketed as NoOps: it aspires to automate all these routine operations [so you can focus on other exciting challenges ;)].
Deckhouse can also be installed on bare-metal servers, provides SLAs & support for those who need.
https://blog.flant.com/wp-content/uploads/sites/2/2021/07/de...