devn0ll

To me the question is more: Is there an extremely valid reason to _not_ use K8s.

As a freelancer I visit quite a number of enterprise companies, think: Banks, Insurance, Airports, and they are all making the switch or are full-on invested in living in K8s by default. If it does not run in or was not made with K8s in mind: It will not be used/bought.

Another thing I'm noticing with smaller companies: If you start fresh, you choose k8s. Which mens all other stuff is already slowly dying by virtue of not beeing chosen.

Developers want/expect it, sysadmins see the benefits from day one, and companies see the potential gains of using less cloud resources and a platform that could potentially run in multiple clouds for the first time ever.

K8s, openebs, prometheus/grafana, loki, kustomize, github actions. This is truly where "it's at" at the moment.

Sure, but think about it: This means other systems will get 16:10 !! (I cannot type fast enough to sooth my enthousiasm for this!)

Some T series, 15 inch, with 16:10 #swoon

Checkpoint VPN. It does not run on Linux so I need to run a Windows VM just for this piece of cr4p software. And it's slow.

Besides that: Jira. (A distant second to Checkpoint though)

Yep me! I couldn't live without those buttons. Especially the Lenovo versions of touchpad and buttons.

Correct! They are indeed unworthy of anyone's attention.

Where I work they use RSA 2fa keys. I have the app on my phone. You would receive a link in the work email, and by clicking it, it would add the token to the RSA app and give you the 2fa keys every 30 seconds.

After a few months, I bought a new phone so I had to get a new link (I thought). But even the IT guys are saying: Nah man that's too hard. Just use the same link you received months ago.

It worked. There is no time-out on those links!!!!. A link we receive in a plain-text email!!! Some of our inboxes are shared / have a PA attached.

But nooooo, this is not a security problem AT ALL... :-(

aaah, ok now my veil before my eyes is clearing up.

So like in: I change a small thing in ansible, perhaps even in an unrelated role, and then check if all is still as I expect it?

"That sounds a lot like "if my code is bad, I'll find out when it breaks in production, so why test?""

Oh no defintely not, no I mean you test and build your ansible and cluster stuff in Development / Acceptance. We create our monitoring checks there as well. And when all that is done and "green": we go to production.

BTW. Testing your cluster is something you do in dev/acc before you go to prod. And Ansible / monitoring already shows you problems in those pre-production stages.

What added benefit is there for Goss in that scenario?

"The tests can be run independently at any later date, helping to ensure that admins haven't messed with important files"

We all run puppet / ansible multiple times a day on our infra right? Checking for config drift.

I'm used to a banking sector where we have extremely stringent demands. And still I see no added value for something like infratest/goss.

Seriously: running ansible on your infra checking for config drift.. is that not exactly the same as running goss? Plus: Ansible returns changes to what they should be at the same time?

Do you have more examples? Because: "is the started service listening on the expected port, is the process of the service daemon running"

can all be done with straight Ansible as well.

I'm just having a hard time understanding the real added value to a goss / ansible combo.

Plus: If you do this after installing with ansible. It's basically a check right? Like: Nagios or other monitoring.

I'd rather that just use THAT and spend time in creating checks in those systems instead of spending time in goss?

For software development those things make sense. Not so much for Operations(?)

I'm already declaring things with Ansible. Unless I got the syntax wrong ansible will finish a playbook and the server will be as I ordered ansible to make it.

So why add another check?

Honest question: Why? Why do things twice? Ansible already promises me to install a specific version of a program, check a certain port (wait_for), make sure a file is owned by someone, etc, etc. If Ansible can't make it happen: it will quit.

Why add goss to the equation?

"Ok, then please tell me your pin code.", "How many times a week do you copulate?", "Can I take a look inside your house please".

"No? Why not, you had nothing to hide? So an automated system is allowed much more detailed information about you and making money with that data? But I can't have a look inside your drawers?"

Even more dangerous to cyclists are the cyclists themselves.

At least in Amsterdam there is something called "Amsterdam Red" meaning: red does not neccesarily mean stop to cyclists.

When a car/truck is parked on the cycle lane they will happily move to the car lane without looking...

Helmets. They are not mandatory, and nobody uses them.

So yes, drivers need to look, but cyclists might want to start following rules and best practices as well.

Partly true, you see: as long as you do not delete the top level "share" everything underneath can be deleted on your machine and it will stay available at crashplan.

I've got 4 TB's worth of photo's (All raw) and want them backed up.

With Crashplan Family: 160 per year. With the cheapest rsync.net: 1500 dollar's per year.

Yeah, not in 1500 years.

That's what I thought as well: http://news.softpedia.com/news/transmission-bittorrent-clien...

This is awesome, finally the real nitty gritty things one needs to know about installing Kubernetes.

None of this `curl http://someshittyurl.io/install.sh | sudo bash` crap.

These kind of docs allow me to understand it, grow from it, adjust to my needs and then automate it using my own tools. (Ansible ofcourse ;-))

We need more of these "The hard way" docs about everything (Chef, mesos, docker, hadoop, glusterfs, etc, etc). Because really: They make things easier to understand.

I'm thinking this would have solved it:

path: "/home/{{ item|default('doesnotexist/') }}"

But yeah, one would do that on test machines first, say: Vagrant on your local machine at least.

It may also make sense to create a user with it's home in a different place, for "just in case" purposes. Or even just use something like freeipa for all accounts.