munki VS werf

In the non-MDM tool space, look into Munki https://www.munki.org/munki/

this experience is an indication that the opco didn't hire the right expertise. If the numbers you quoted ie 30k desktops, 50k total were not macs, it's clear that the org didn't have the kind of mac experience needed to manage a a new org with all macs.

It's entirely possible for administration of macs.

Start networking/asking around with places like Disney or Pixar, etc which have a large amount of graphic artists using macs. For example, from Disney https://github.com/munki/munki gets you to a certain point.

Other tools like Kandji (lightweight) and the 900 lb gorilla in the industry Jamf gets you the other management / administration bits needed

If this opco that you referred to never got a Jamf rep to work with them and to try out their (yes, very expensive) products, then this is mostly inexperience with the mac ecosystem.

There's a decent open source option: https://github.com/munki/munki

I got to use it at work at Meta (as end user), and it seemed to work quite well. They delivered Android SDKs/IDEs and a bunch of other things that I'd personally install through Brew with Munki.

Munki is not an MDM and I recently learned there's this project called Installomator that might help.

Or Munki

This is a feature of munki called default manifest resolution. Though I prefer to avoid this and explicitly set the client identifier for all devices.

another option is munki https://github.com/munki/munki, for the software update part,

I am looking as well for this kind of tool. I just took a look today by exploring the CNCF landscape this tool : https://werf.io/ , I haven't used it, but it seems to take care of painful stuff like automatic versioning for example. (If someone here tried it, I will be happy to listen to your feedbacks)

Werf - um ok

HybridK8s Droid - Intelligence foor your favourite Delivery Platform Devtron - Software Delivery Workflow for Kubernetes Skaffold - Easy and Repeatable Kubernetes Development Apollo - Apollo - The logz.io continuous deployment solution over kubernetes Helm Cabin - Web UI that visualizes Helm releases in a Kubernetes cluster flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) Kubeform - Kubernetes CRDs for Terraform providers https://kubeform.com Spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. http://www.spinnaker.io/ werf - GitOps tool to deliver apps to Kubernetes and integrate this process with GitLab and other CI tools Flux - GitOps Kubernetes operator Argo CD - Declarative continuous deployment for Kubernetes Tekton - A cloud native continuous integration and delivery (CI/CD) solution Jenkins X - Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Tekton, Knative, Lighthouse, Skaffold and Helm KubeVela - KubeVela works as an application delivery control plane that is fully decoupled from runtime infrastructure ksonnet - A CLI-supported framework that streamlines writing and deployment of Kubernetes configurations to multiple clusters CircleCI - A cloud-based tool that helps build continuous integration and continuous delivery pipelines to Kubernetes.

Check out https://werf.io/ tool. It features giterminism which is somewhat similar to gitops, but it does not require pull model. Giterminism aims to improve reproducibility of your build and deploy configuration. werf also features content-based-tagging out of the box, which allows creating immutable images, stored in the container-registry, shared between multiple runners (werf uses distributed locking to prevent overriding image which is already published). Giterminism and content-based-tagging enables easy rollbacks to any git-commit in the history of your project. By design werf could be embedded into any ci/cd system.

Rename of dapp to werf was in Jan'19 to be precise (https://github.com/werf/werf/pull/1213).

Werf

You can try werf, it has Helm under the hood and there are github actions available for it: https://github.com/werf/actions

As you know, there's plenty of tools that can be used to build your Docker images, besides the docker build itself. werf is an Open Source project with a long history (started in 2016 as a simple wrapper around Docker CLI). Still being a CLI tool, today it is focused not just on the building but also delivering these images to Kubernetes — and this is what makes it really different.