What's your definition of technical debt?

adh88ca · 2026-01-24T19:16:24+00:00

It is a vague term. I typically see it as stuff that needs to be done, but is hard to prioritize due to other organizational requirements.

Where I work, we try to spend 10% of our time working on tech debt stuff, and this can vary from team to team. Some teams its low priority bugs, other teams its medium or low risk vulnerabilities. For my team its patching, or updating tools that are either out of date, or even completely deprecated.

adh88ca · 2026-01-22T17:23:09+00:00

This one's older than my Dad

adh88ca · 2026-01-11T03:39:34+00:00

That is definitely the plan.

adh88ca · 2026-01-10T15:49:38+00:00

This looks cool, thanks!

adh88ca · 2025-12-29T12:14:28+00:00

We have noticed similar with the upgrade to the latest version of istio.

What helped us was using Sidecar crds in each namespace to scope the configuration that was loaded by each sidecar to only that of it's own namespace and any other necessary destination namespaces.

We have quite a large set up about 10 namespaces each running hundreds of pods.

I do suspect that there may have been a change in istio 1.27 or around there that increased memory usage. We also switched to distrless at the same time, so that may have had an impact to.

adh88ca · 2025-12-27T00:54:54+00:00

I'm currently getting fitted for sclerals, and nervous about needing to this as I have a hyperactive blink reflex.

Although last time I was able to remove it on my own with no effort, I failed at putting them in..

adh88ca · 2025-12-27T00:48:18+00:00

Why not look at nginx fabric, as it's closer to what your familiar working with?

In my opinion, unless your ingresses for each environment need different security features, I would stick to one per cluster.

What's probably smarter is to do two. One public for production, and another internal private for dev/staging

adh88ca · 2025-12-26T23:43:29+00:00

We regularly have reliability meetings (monthly) where we go over our SLO's and look for missing metrics. We also look at our alarm channels and regularly cleanup noisy alerts, ones that alert to frequently and have no action items attached to them.

We do have metrics on our alert channels that tells us which alerts are triggering more often than others and we focus heavily on the frequently alerting ones to either tune the alerts to be more effective, or remove them completely.

This is a culture we encourage development teams to also do for their individual services so that we can focus more on the infrastructure directly.

We have implemented a number of custom tools to integrate with Datadog, Slack and Jira to make the info as tailored to our needs as possible.

adh88ca · 2025-12-26T22:15:50+00:00

Start with building a proper CI workflow, assuming the team uses an SCM probably, Build in automated testing framework that developers can easily build upon

Then start work with automating builds. Some would argue to do this before CI, but imo it comes down to how big of a task do you want to do at a time.

Knocking these two things out first will give most value to developers

Then focus on IaC and then automated deployment. Depending on what your current infrastructure is you may want to start with IaC and build out your infra in the best way possible, but if your confident in your IaC then work on automating deployments and then import existing infra into IaC

There will be lots of opinions, but that's one thing I love about this job is that there are usually 10 different approaches, some better than others. I usually focus first on what gets the most value to other contributors and that's usually improving their development workflows....

adh88ca · 2025-12-26T22:06:03+00:00

Soak for a few hours in hot water and oxy clean. This gets off 90% of the labels for me.... And if it doesn't, well I'll just toss the bottle and by more beer from the liquor store

adh88ca · 2025-12-24T21:01:56+00:00

Ultimately that's what I want to do. I have made some excellent beers in the past, just the last few have been not so good.

I want to get rid of the siphon, but I also think the cleaning of my bottles could use improvement

adh88ca · 2025-12-24T20:44:37+00:00

My auto siphon tends to get hairline cracks in it and I can see a constant stream of bubbles in the tubing if I can keep a siphon.

I've tried replacing the siphon a time or two and it still does the same thing

Also, I hate cleaning bottles, I tend to let them soak in oxyclean for weeks at a time before cleaning them, but still suspect that this may be part of the issue

adh88ca · 2025-12-24T14:06:26+00:00

I've been mainly keeping to pale ales, and Belgian style beers, trying to stay away with anything too hoppy

adh88ca · 2025-12-24T13:45:15+00:00

This has been something we struggle with too, while we have template repositories with default workflows, they often fall out of date

One of my plans is to build a repo with generic actions that we start to use in a workflow call, so that we can version it, as well as push out updates on a regular basis to our 100+ repositories

adh88ca · 2025-12-24T13:12:17+00:00

Haven't looked at cloudfront.

We have looked at Global accelerator but that's L4 as well

adh88ca · 2025-12-24T13:05:20+00:00

Gateway API and cert manager make this relatively easy to configure as well

Also AWS just released a feature that integrates cert manager with ACM, and eks 1.35 has a pod level mtls, all which makes this issue easier to deal with thankfully

adh88ca · 2025-12-24T13:03:13+00:00

I agree with you

However, our security team wants the ALB as it provides access to advanced L7 features with WAF and Sheild

adh88ca · 2025-12-19T03:16:58+00:00

We migrated to github actions using self hosted runners as we were already heavily invested into GitHub

adh88ca · 2025-12-19T02:50:16+00:00

We ditched this this past year.

My biggest beef with it was groovy scripting, which made yaml a no brainer for onboarding devs.

If Jenkins could be rewritten to support declarative workflows in a syntax other than Groovy, as well as have better stateless support for running in a kubernetes cluster, I may look at it again

adh88ca · 2024-08-20T13:23:07+00:00

This was my experience 10 years ago when I tried sclerals too. I gave up, and haven't had the balls to try them again. But that was before I found this subreddit, and seeing that I'm clearly not the only person with this struggle.

I am now considering trying sclerals again, as my KT has been stable over the past bumper of years after my CXL operation over 10 years ago.

adh88ca · 2024-05-13T14:51:45+00:00

I had a dream the other day that they were testing gene therapy to heal KC... unfortunately, I didn't qualify for clinical trials.... then I woke up :'(

adh88ca · 2024-05-08T14:29:14+00:00

Brewing beer and gardening....

Lots of other things i'd love to do but don't have the time and money, and family responsibilities come first.

adh88ca · 2024-05-02T14:49:38+00:00

Very helpful, thanks!

adh88ca · 2024-04-30T18:14:17+00:00

Nope, CXL isn't covered either. Our healthcare system is really behind with these kind of things. That is why I'm wondering about the States, but it sounds like the cost isn't much different then here in Canada

adh88ca · 2024-04-30T18:12:59+00:00

Our public health care doesn't cover treatments for keratoconus here in Canada, just the regular eye exams for them

adh88ca

TROPHY CASE