Reply to post: Re: K8s a use case: Enable Self-Service

'Boringly reliable': Red Hat architect thinks Kubernetes is 'mostly done' – but there are still plenty of bugs

sed gawk Silver badge

Re: K8s a use case: Enable Self-Service

So k8s is hideous, it's sprawling, complex burdened with stupid names and written in yaml.

But it's about self service, when I have a templating problem, I reach for sed.

K8s gives them an override file to change a line, and a special command 'kustomize' which exists exclusively to change a line in this sort of yaml file. I didn't know this existed but it's really a thing, and now it's adopted into the main kubectl command with the -k flag.

So a way to look at it is an output target for various tooling, the result of which are some yaml.

So your scripts queries a db, runs perl over the results and spits out some yaml which k8s interprets.

The commands are verbose but sensible once you grok the concepts. You can run shell scripts with environment variables being injects from various useful sources, which something genuinely useful when combined with replication.

So I can tell a user, here is the platform contract, use the following env-vars in your service/script and the configuration management will do the right thing in development and production.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon


Biting the hand that feeds IT © 1998–2020