#random (2024-09)
Non-work banter and water cooler conversation
A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels.
Archive: https://archive.sweetops.com/random/
2024-09-04
2024-09-09
2024-09-10
:wave: Hi everyone, I’m looking into the Atmos project and I want to say it’s awesome, it should make our lives easier. Can you please tell me if it is possible to specify a single component or a group of components and exclude one or more components during the deployment? That is, we need to be able to have multiple engineers working on the same stack and if someone makes a change, they can roll back the changes of another colleague. Of course, we can look at the plan, but is there a possibility to just specify what should be deployed? There are commands in terragrunt: --terragunt-include-dir, --terragrunt-exclude-dir, --terragrunt-strict-include, --terragrunt-ignore-external-dependencies, etc. We need the same in Atmos.
Thanks @Petr Dondukov for the kind words
Best place to ask usage questions is in atmos
2024-09-11
2024-09-12
Recently I worked on Gloo Mesh Enterprise. It is a commercial version of Kubernetes Federation (obsolete). Here is the multiple cluster settings, https://docs.solo.io/gloo-mesh-enterprise/latest/getting_started/multi/gs_multi/.
What was the use-case?
multiple cluster mesh and API gateway
still feel it is too overkilled lol
Or I mean what problem was the business hoping to solve
seems to me it is an enhancement on top of service mesh
kube federation is obsolete, and there are other alternatives, but not being used a lot in real projects
2024-09-13
You guys ever consider selling swag that says “insane cloud posse” or just “cloud posse” swag ? Id wear it around if it wasnt too loud
Yea we are overdue for this. Whats the best platform for this these days?