引っ越してから電気料金がおかしい。確かに一人だったものが二人になっているが、それは別に電気を２倍使うわけではない。３倍おろか。なのに報告されている使用量はそうなっている。参考までに去年の該当期間は346kWhで、今年の同期間はまさかの956。いくらなんでも増えすぎ。
結局二人暮らしと言っても、在宅で働いているという一日のほとんどの時間を占める消費は変わっていない。それに使っている機材も変わっていない。エアコンは２台から３台に増えてはいるが、それもずっと全部起動しているわけではない。冷蔵庫は変わったが、逆に省エネ基準が高いやつになった。
I ran into a really weird problem today. I noticed some strange config drift on one of my nodes (shit happens when I manually experiment in “production”), so I decided to reinstall/upgrade the k3s agent. For a while now I’ve been connecting my nodes through tailscale, so that I can have my homelab machine join the cluster from my home network as well. k3s has a(n experimental) feature for “natively” integrating with tailscale and it’s been working just fine so far.
よくある話でしょう。金は儲けてるはずなのに、貯金（投資）が貯まらない。大した買い物はしてないはずなのに、クレカの引き落とし額が面白くない数値になっている。
さすがに歳も歳なので大人らしく口座の残高を気にしようと思った。まぁ学生の頃は金欠に大人らしいとは言い難い、口座を気にせざるを得ない状態だったけど、今は違う。と思いたい。
Usually there was no problem. Stuff worked just fine. Certificates were generated and renewed automatically. https:// links opened without ugly browser warnings about how you’re about to get hacked and it’s the end of the known universe.
But when it wasn’t “usually”, when Traefik just happened to restart for whatever reason, then all of that was obliterated. Since Traefik was running on ephemeral storage, eg nothing was really persisted, innocently tweaking some configuration (that resulted in a restart) could be catastrophic. You know, self-signed certificates and ugly browser warnings.
I’ve been using Argo CD for GitOps automation for a very long time. I have it manage itself too! The other day I noticed that there was a new major version of Argo CD, so I decided to upgrade my stuff too. It did not go smoothly, though it wasn’t an issue with Argo CD itself.
It was the usual problem of Helm charts renaming and moving around stuff in their values.yaml, which results in significant breakage for (from an user perspective) no good reason. I summed up what I learned so others don’t have to play around with it so much.
I’ve been playing around with smart lights for a while now. I have four Edison Smart filament bulbs, two Philips Hue white bulbs and some Switchbot bulb. I had a terrible experience with Switchbot bulbs (which is why I got the Hues in the first place), disconnecting and needing to be re-paired all the time, suddenly factory resetting themselves to max brightness in the middle of the night and such. So the one I kept is just a reading light now with a manual switch on my bedside table.
For the others though, I’ve wanted to have some manual switches for them too in addition to being able to control them through my smartphone. When I get home it’s still quicker to tap a physical switch than to whip up my phone, wait until the respective proprietary app connects to the bulbs and then I get some light.
What I ended up with: a Home Assistant Green with the external USB Zigbee dongle, three IKEA RODRET switches and this blog post. I got those Home Assistant devices because that’s what I could get shipping to Japan, but I believe the Yellow version has Zigbee built in, which should make it a little less clumsy.
今年初めてスーパーアリーナのVIVA LA ROCKの3-4日め行ってきた。目当てのバンドも楽しかったバンドもいっぱいあったが、最終的にもっとも印象に残ったのは花冷え。だった。
So often I see people giving talks about how the microservice architecture is a failure. You end up losing transactional protections, you’ll have to “join” data across a network boundary, and that network boundary is “always” flaky. Wouldn’t it be much better if everything was in one process, where you could enjoy the benefits of transactions, neighboring data is just a method call away and the only network you have to worry about is the database connection?
