Brandon Philips
Brandon Philips
This is an "emergency" procedure that requires root but can be done: Edit `/etc/coreos/update.conf` to the desired channel. ``` cp /usr/share/coreos/release /tmp mount -o bind /tmp/release /usr/share/coreos/release ``` Edit `/tmp/release`...
Kubernetes keeps an event log that can be viewed using `kubectl events`. But, many people would also like to have these events go to their centralized logging system as well....
In a production configuration Kubernetes has a number of points that should be monitored. This document describes points that should be monitored externally and on-host. Doing this sort of monitoring...
We have it in advisory mode, now tell users how to enable it. @mjg59 could you take a swing at this?
write something based on this thread: https://groups.google.com/forum/#!topic/coreos-user/YLq2WcdSi20
If a machine doesn't have the selected IP type it is silently dropped from the list. This can be annoying to debug if you don't know what is going on....
I probably won't have time if someone finds a bug :) Help wanted.
As quayctl creates a one-shot registry perhaps it is just best that quayctl serve this up and not talk to container engines directly. This would make it possible for someone...
We can take inspiration from this guide for rkt: https://github.com/coreos/rkt/blob/master/Documentation/devel/release.md - How are the cross platform builds done? - Where is the image version bumped?
It would be nice to add https://docs.sigstore.dev/signing/signing_with_blobs/ to the build automation. Down the line I would like to build an Obsidian plugin that validates the contents of plugins against sigstore.