4 comments

[ 2.9 ms ] story [ 23.1 ms ] thread
> Kubernetes, Istio, knative and an internally developed specification for “hardening” containers are now the default software development platform across the military.

I'll go back and read the rest after I've stopped laughing. But seriously, no. Not the default platform across the military, not by a long shot. DOD and defense industry dev is woefully behind the times with a few pockets of "oh fuck, they're ahead or caught up with industry". By a few, I mean touching somewhere around 0.0000001% of the total work, maybe less.

I saw Chaillan's name and description as USAF CSO while reading the article and was confused, he left in 2021 and checked the date of the article. This was published in December 2019, that line is even richer coming from over 3 years ago.

The whole thing was a demonstration project. It's still going on, but even now (3+ years later) it's far from the standard way of working.

Definitely an old article but a lot is still moving along in the DoD cloud native space. The article mentions Platform One, which has done a lot to provide open source resources for those using k8s within the DoD community.

There was a decent number of people who left Platform One and started Defense Unicorns. If you are interested in disconnected k8s deployments, checkout their open source project Zarf. - https://zarf.dev/

They also have an interesting OSCAL compliance through kyverno project called Lula. - https://github.com/defenseunicorns/lula

Yeah there are a ton of offshoot projects that arose from Platform One for sure.
I work in the disconnected k8s space. It is definitely exciting to get these platforms (that by and large assume Internet connectivity) running within airgaps. The sneakernetiness of it all is the most fascinating bit for me.