In my experiments with SpecKit I was always left wondering "when does it merge all this specs into a single ground truth". I never got there and it felt like a huge missing step.
Now I'm left trying to define/design what a "spec" for communication between humans and coding agents would look like, to power what Birgitta called spec anchored.
I feel like "a hold my beer" version of this just accepts webhooks from your artifact registry and pre-pulls new versions of running images, or maybe images that node has seen in the last X hours
I had written the wittiest of emails, clicked 'Send', and the button just went grey. No other signals. I hit refresh, ignored the warning about losing data, autosave drafts FTW right(?!).
They only show a snippet because they can't sell your eyeballs via the RSS feed. They need just need to drsw you to click onto their full site to blast you with ads.
The kubernetes community is pouring a lot of resources into cri-o. I imagine you are going to see the kubernetes clusters that are built 'the hard way' start switching over and removing docker. It will still be used for building pushing containers for the time being.
It's definitely a tricky space to navigate. If it were a private network you may be able to discourage false accusations.
I've heard of 'whisper' networks which warn people of unscrupulous behavior from colleges when they join new workplaces. It could be the realization of that concept.
That was my initial thought as well. CRI-O hits 1.0, and then this. To me, it comes across as an attempt to stay in the news. Possibly to start changing the narrative from Docker vs Kubernetes to Docker <3's Kubernetes.
Now I'm left trying to define/design what a "spec" for communication between humans and coding agents would look like, to power what Birgitta called spec anchored.