After Plaza Argentina base camp, we kept doing the same load carrying routine: carry up some team gear, go back down, maybe rest and then move to the higher camp. We had a total of three high camps: camp 1 at 4950m, camp 2 at 5570m and camp Colera at 5870m. While we were climbing Aconcagua the “Polish traverse” route, Colera is also the highest camp of the “normal” route.
The route up to almost 7000m altitude on Aconcagua is a long one. I’ll write about the “world below” (Mendoza and the area) later. Our route, the “Polish traverse” goes up the Vacas valley to the base camp at Plaza Argentina. On the way we had lunch at some roadside restaurant where we met another team (of two + guide) who were going up the “normal route.”
If you’ve watched Yama no Susume, then you’ve heard of Mt Tanigawa. It’s the goal of a major arc of the story and an important memory to the characters. I went there in a different season though (in the snow), but didn’t climb the main summit. For no particular reason other than I didn’t realize the summit I was at wasn’t the highest point. Whoops.
This year was quite thick in events so I decided to write a year retrospect for a change. I read somewhere that people tend to do wild things when they’re nearing a “round” age like 30, except I read about this after I planned most of the stuff listed below… It definitely did turn into a very eventful 30th.
I wish it could be completely automated… But for now I’ve just automated as much as possible (and convenient). The ingredients:
I have a repository for the purposes of playing around with Kubernetes tooling like this – and hopefully turn it into an actual application eventually. I have big plans and lots of stuff I want to try out, but time is limited. All the code examples in this post use the namespaces and naming choices in the repository. The folder structure (relevant to this bit) is like…
system
├┬ apps
│└─ (bootstrapped Argo CD app manifests)
├┬ argo
│└─ the local "umbrella chart" for Argo CD and Argo Rollouts
├┬ bootstrap
│└─ boilerplate project and application manifests
└┬ manifests
└─ manifests I didn't bother turning into a Helm chart
referenced by the raw-manifests.yaml application
We’ve got a printer in the office. I’m not sure how the network is organized, but it’s on a different IP range than the rest of the dev network. And for some reason I couldn’t get it to work.
Mitake with its ropeway is probably “the” hiking destination in Tokyo. It’s accessible, not particularly high and you still get beautiful views. Oh, and crowds. Of course crowds.
I’ve had most of my stuff running a k3s “cluster” for the past half a year or so. The whole setup runs on a single $5-a-month Digital Ocean droplet with 1vCPU and 1GB of memory.
Needless to say, it doesn’t take much to bring the whole thing to its knees. While it has no issues dealing with the little traffic my blog receives, I would accidentally bring it down occasionally when I install a Helm chart that turned out to be much heavier than I’d thought.
Not the carrier. Not the anime. The mountain. (After which the carrier was named, by the way.) It’s not one of those jagged, snow-capped “cool” mountains. It’s a relaxed, even comfy mountain. At 1400-and-a-little meters high with gentle slopes, it’s a good day’s escape from Tokyo’s chaos.
After last year, I once again decided to take part in the Hacktoberfest fun. I have plenty of repositories lying around (sadly much less well maintained by yours truly than preferable). Of course this also means that I can gather the necessary contributions from updating dependencies in my own repositories, but I’d prefer to instead contribute to those dependencies.
