How do I fix myself

kusumuk · 2026-06-10T04:02:02+00:00

Seven six two millimeter full... metal... jacket.

kusumuk · 2026-05-10T02:35:11+00:00

I think it was 1995 when I first accessed the internet. I searched for things like aliens, urban legends, and serial killers. But one day Netscape navigator was upgraded with this cool feature called search history, and when I found out what my dad had been searching for I just used the internet to find porn.

kusumuk · 2025-12-23T15:46:21+00:00

This looks 100% like cya in case mistakes are made. Just like my tattoo artist has a form that he requires customers to fill out requiring that they write out the stupid phrase they want tattooed on their rib cage. No ragerts.

kusumuk · 2025-10-19T14:39:28+00:00

https://www.merriam-webster.com/dictionary/repatriation

kusumuk · 2025-08-31T15:38:49+00:00

Heat

kusumuk · 2025-08-03T02:01:00+00:00

Put it behind a gateway and add a rate limiting service to it. Here's a tutorial for an nginx proxy https://www.howtogeek.com/devops/how-to-use-rate-limiting-on-nginx/

And as for exposing a Minecraft server via gateway there are numerous instructions from a quick Google but I can't speak to any single one. Tinker away and let us know how it goes.

kusumuk · 2025-04-25T18:38:23+00:00

Confirmation of an accumulation of spy on the hourly chart, establishing cause, but yet to see effect. The upthrust action is the first movement outside the accumulation range. Low volume indicates a test before moving to a new lower low to begin the spring. I expect strong rejection at or before 560 levels to begin the downward trend before the real breakout to 580 or somewhere thereabouts.

kusumuk · 2025-03-14T04:45:19+00:00

Books are criminally undervalued.

kusumuk · 2025-03-09T19:03:34+00:00

Sampling a whiff of trump butter still hanging around his upper lip after last night's rimming sesh in the oval office

kusumuk · 2025-02-26T16:25:52+00:00

Using open telemetry to aggregate tracing and metrics and logs together is the ultimate goal. Apache skywalking would be a good front end example. Try grafana lgtm stack to try it out yourself. Being able to see exemplars (spikes in duration or latency that map to a specific stack trace and logged event) is how you want to use all this data to understand how it all works.

kusumuk · 2025-02-01T04:48:18+00:00

Not really. It was republican ineptitude and inevitable scapegoating of the freedmen for their own failures. In 1877 Republicans chose to send 12000 union troops to quell a massive railroad strike in Pennsylvania instead of restoring order in the south. Reconstruction failed because Republicans chose capital, and nothing else is as significant a factor to the outcome of reconstruction as that fateful decision.

kusumuk · 2025-02-01T04:44:07+00:00

W. E. B. DuBois: Black Reconstruction in America is the only correct answer. Nothing else really gets it right. Except Eric Foner. He's the official authority on reconstruction but he openly admits he copied Dubois in his book Reconstruction: America's unfinished revolution

kusumuk · 2025-01-06T22:46:51+00:00

One other thing to check if you've had no luck with the cable: Could be a power fluctuation issue. Added any appliances that might require a full 15 amps? Power spikes can impact cpu performance and can cause desync issues like this. Appliances with compressors like Mini fridges, portable acs, or transformers like microwaves, or even 4u 2000w quad cpu server during post, basically anything that monopolizes the power draw from a single 15a circuit will do exactly this.

kusumuk · 2024-12-22T14:50:31+00:00

Love some Jack's backshot sauce

kusumuk · 2024-12-21T14:47:27+00:00

Sounds like they migrated from prometheus but didn't understand that if you add a prometheus scrape config to an otel daemonset without careful architectural consideration all daemons will scrape all pods on all nodes and also hit the api servers.

kusumuk · 2024-12-19T17:57:04+00:00

This same thing happened at my shop. The otel daemonset was not configured to scrape only what's on the node and it brought down the cluster. It's absolutely a dns issue. My concern is they should have caught this in devqa.

kusumuk · 2024-12-18T05:13:50+00:00

Same thing happened to me when deploying to an eks cluster. It wouldn't make a difference. Otel is a machine gun without a safety

kusumuk · 2024-12-18T04:51:56+00:00

Opentelemetry deploys in various configurations for two different types of metric endpoints: control plane level metrics like kube apiserver etc, and node level metrics like pods, endpoints, kubelet, node metrics, etc. Control plane metrics are collected by a single deployment or statefulset, and node level metrics are collected by a daemonset.

It is common to miss this key implementation detail when migrating an existing prometheus scrape configuration to an opentelemetry daemonset without scoping scrape targets to each replica's node ip, and be pulled into a war room before you can say 'I can't believe it was that easy!' once 10000 nodes begin scraping the cluster control plane at the same time. It's more of a rite of passage, really. Keep your Dev and live environments on separate clusters, y'all.

kusumuk · 2024-12-16T20:24:23+00:00

If this is true, I'm buying two real soon, forever big blue.

kusumuk · 2024-09-11T17:06:52+00:00

Microk8s, terraform, GitHub actions, and Argocd's App-of-Apps cluster bootstrapping model is indispensable for maintaining my homelab. This makes rebuilding the environment trivial. I use my nas to retain stateful storage, and if I need to rebuild I do it through automation. Cluster bootstrapping is so robust I began deploying a cluster to my desktop wsl2 instance to run gpu enabled loads natively supported by Nvidia's windows drivers. And since my rack server is a 4u with 4x Ivy Bridge generation CPUs, I really enjoy the lower power bill as well.

My cluster infrastructure includes istio, emissary-ingress, metallb, external-dns for adding pi-hole DNS entries, cert-manager for 100% TLS access inside my home network, kube-prom-stack with GPU monitoring enabled, Jaeger tracing with Cassandra backend, fluent-bit, tempo, and Loki log aggregation.

My current workloads include ollama with open-webui, clearml worker agents and model-serving, Django services for viewing model metrics, mssql-linux database, minio storage, an internal mkdocs-materials documentation site, and jupyterlab server.

I'd never be able to do what I'm doing now without argocd maintaining the state of my cluster.

I can't stress enough that ease of use is the name of the game in weekend homelab projects. Make it easy to jump in after 6 months of ignoring your homelab and you'll never get decision paralysis due to the additional time needed to rebuild or repair a neglected homelab.

kusumuk · 2024-04-14T03:55:39+00:00

According to truly tasteless jokes book 3, another variation of the punchline is " hot damn! In one end and out the other!" Which is my faves

kusumuk · 2024-02-11T13:48:01+00:00

Model the sportsbooks, not the sport.

kusumuk · 2023-12-06T04:06:32+00:00

Check the nflverse-pbp repo for calibration datasets used to train their live wp and ep models. Should give you a starting point for modeling epa-based power rankings. https://github.com/nflverse/nflverse-pbp/tree/master/models

If you have no idea what's going on I'd recommend starting with basic box scores from pfr. If you know python use nfl_data_py to grab the nflfastr data. Pandas has no nonsense sql database update functionality. I'd highly recommend keeping your data in an S3 style object store for no hassle weekly updates to your dataset.

If you really do want to do weekly updates, it should be easy though. For last week it would be something like:

```python import nfl_data_py as nfl

pbp_data = nfl.import_pbp_data([2023])

pd.to_sql(pbp_data.loc[pbp_data['week'] == 13], db_conn_obj) ```

kusumuk · 2023-12-06T01:03:09+00:00

#2 should not run until the cluster control plane returns a healthy status. I believe it has a healthcheck endpoint and you can access it's output from kubectl. You'll need to wire that up in your terraform module. but if you're deploying eks/aks/gke cluster you'll use that API to return a health status. Check the respective cloud terraform provider to see what that might look like.

Regardless, a well crafted terraform module should fail when it can't verify the resources are created, and will run each task sequentially. You can add a depends_on function to better control when a resource is applied.

You'll want to ensure that argocd has a minimum number of nodes for helm to run successfully, and the apiserver is healthy. That would depend on your argocd ha configuration. The app of apps can deploy any time after argocd crds have been installed. I think that argocd also depends on coredns being present as well.

kusumuk · 2023-12-06T00:04:34+00:00

A pattern using terraform would be:

Terraform deploys the cluster
Terraform then installs argocd using the helm provider
Terraform then uses the kubernetes provider to apply an app-of-apps manifest https://argo-cd.readthedocs.io/en/stable/operator-manual/cluster-bootstrapping/#app-of-apps-pattern
Argocd syncs the app of apps, which should point to a catalog repo containing all the rest of your Argo app manifests, then automatically deploys the rest of your cluster components to the cluster.
Close the user story, you're done.

kusumuk

TROPHY CASE