scndalousarbite

5 lat temudiscuss

No. Entrepreneurs understood our cultures tendency towards vanity, self reflective and voyeuristic exhibition, and created businesses based on this. Social media was the exploitation and exaggeration of that vanity. What it is now is a huge business and opportunity for marketing and social control.

scndalousarbite

5 lat temudiscuss

Hmm. The expectations and engineering of a platform like kubernetes and 'fail till right' require a lot of alignment work to get to the point where 'fail till right' works.

There is no silver bullet. Automation and self healing is a selling point but when it hits engineering it usually is a dud in terms of incorporation in existing environments.

The real novelty would be to generate a declarative description from the customer and provide an in place deployment solution via k8s. That would be the ultimate replacement solution.

scndalousarbite

5 lat temudiscuss

qemu/kvm and libvirt as an example api to address your resource idiom + a load balancer/rev proxy API. You are missing my point afaict.

scndalousarbite

5 lat temudiscuss

Nonsense. Social media and the sensational, vain culture it has inculcated it is entirely damaging and without value. It is _only_ revolutionary and disparages any prior merit and censure without reason. It is a denial of service on reason and experience claiming precedence and priority without any historical context.

scndalousarbite

5 lat temudiscuss

That allow for rollback/rolling, seamless or canary transitions and encapsulate the entirety of a mature release cycle into a declarative operational rubric? None I am aware of outside of k8s competitors.

However I think this value can be oversold and it is a simplification of processes that were used before k8s to achieve the same end.

Say that I have v1 ready for release and want 20% of my users to hit those endpoints in prod. Simply done in k8s. Also simply done with rev proxying and automated configs in nginx + custom app provisioning _without_ k8s in announced maintenance. None of these ideas lives in isolation.

scndalousarbite

5 lat temudiscuss

Like sched_setaffinity didn't exist and cgroups can't be used outside some container env?

scndalousarbite

5 lat temudiscuss

Playbooks are terrible. They are a replacement for expert knowledge of platform tooling. There is no replacement for expertise and knowledge of the platform.

Serious problems are always reduced to understanding the platform, not the playbook. Ansible and the python ecosystem are especially broken. I will _never_ use another playbook to replace mature ssh driven deployments.

scndalousarbite

5 lat temudiscuss

k8s is not simple to learn for legacy admin teams, even those who have some container experience. It is simple to kubespray a semi-working cluster on-prem or cloud provider k8s your way along but if you need to actually learn how to deal with multiple ingress controllers, a service mesh, need multiple storage providers, affinity, gpu accelerated apps, secure k8s and the other problems solved in the legacy world (in myriad ways) k8s can be regarded as a disruptive interruption in your ability to operate. All this being said I lead both IOT edge(via k3s) and science (cloud & air gapped 'vanilla' k8s) platform teams and appreciate the chance to sell k8s and make easy money.

comments