Welcome to Brent Cetinich’s Blog!¶
Here is a list of most recent posts:
19 June - Nixos ydtools permission denied socket
To get
ydotoolrunning on Nixos Plasma with KDE you just need to:18 June - Nixos Blutooth cant enable after disable
On my a Lenovo Z13 Gen1 with Nixos / KDE Plasma 6.0.5 after the laptop goes into power saving mode the bluetooth adapter enters some kind of degraded state where it does not work properly, for example random disconnects or intermittent lag on bluetooth mouse or the device disappears all together.
18 June - Native K8s Sidecar Containers with gluetun
I tried to use the new Kubernetes native Sidecar Containers introduced since v1.29. The
initContainersand pod were stuck inPodInitializingstate and the other containers were not starting up.18 June - External-DNS Policy flag
The behavior of the external-dns
--policyflag is not documented in the external-dns docs. After looking at the code and experimentation the flags work like this:18 June - Deploy to K8s using helm without helm
On many occasions helm is not available directly on my cluster or I do not trust the author. So how can I deploy to my cluster without helm? Luckily helm can be configured to dump the template to on disk yaml manifests that can be applied to the target cluster. If you do not pass
include-crdsthen no CRDs will be output and you will get errors later where CRDs are missing.18 June - Cert-manager can’t find route53 secret
It seems I did something to delete the original cert-manager Route53 secret, renewals and new certs failed with this error:
18 June - Airpod reconnecting on Nixos
On my Apple Airpods Pro connected to Nixos vie bluetooth with KDE plasma, I get constant disconnect and reconnecting tones in the headset. The logs show this and the device number keeps incrementing after every reconnect:
18 June - 10GB Thunderbolt Other World Computing OWC Arch Linux
The device does not show up in arch linux until the thunderbolt security mode in BIOS is set to “Legacy” It is based on the AQC107 chip and drivers are provided.
02 January - Opensearch failed to obtain node locks error
My cluster would not start up after killing the containers using the
force, which means elasticsearch / opensearch did not get a chance to cleanly shutdown and remove the lock files. The error looks like this:02 January - Feline stationary angular momentum exercise habits, a temporal analysis.
