People can surprise you.

So the fellow I was so grumpy with got back to me.

He apologized. I was surprised but pleased – doing the hard *things are never fun, but they separate the grownups from the kids.

I thanked him, I’m willing to give him a pass on the next time he’s tense and misdirects.

* I felt this should be ‘is’ instead of ‘are’, but it’s plural and not singular, so I believe it’s correct, even if it doesn’t seem to look that way when I read it.

If you’re going to complain about it in private…

Then it’s obviously bothering you.

With that in mind I took the time to write the person involved in the last post directly, and explain how our last conversation had played out. What he’d said, what I heard, and how that both annoyed me and made me question unspoken limits.

I left him with a series of questions hopefully designed to clarify whether or not there were some unspoken rules I was breaking.  Now to see if he responds.

Like so much of life, this too is a test.  There are a lot of ‘correct’ responses.  Only one or two of those include anything that makes me happy.  The only really wrong response.. is no response at all.

How he responds (if he does) matters quite a bit to me. There’s a chance we’ll be actively working together in the future. If we are going to have issues, I’d rather know now, so that I can start preparing other options.

Sometimes I get frustrated.

I’ll admit it, I’m annoyed.

I saw a coworker ask for something to be set up.  I had just finished setting up exactly that for another team, so I offered to either to the work, or show him how to.  He was interested.

Meanwhile the team he’d initially asked came back to him, they’re too busy for a month or two.  That’s believable.  I mentioned to their lead I had made this offer, and it would therefore be something they didn’t have to worry about, unless they wanted to own it.

His response irritated me.  He didn’t like the technology I was using.  I gave him my reasons, and mentioned it would be a rapid setup.   He said X other way would be faster…

All the while, I’m thinking “Huh? You’re not going to be doing the work for at least a month, so it’s not really faster is it?  I mean if it was as easy as you’re saying, why the hell are you pushing this other guy off?  Why do you dislike my solution so much, especially if it reduces the amount of work you have to do?”

I managed to stay polite, but I was pretty offended.  I offered to walk back my offer (thus taking the role of bad-guy), and even that didn’t provoke a reasonable response.

He’s not my boss, and I’m pretty glad about that.  I like being appreciated, and having someone back-seat doubting my decision was pretty demoralizing.

I say again he didn’t like my solution, but was not going to provide an alternative within a reasonable period of time.

 

A challenger rises.

Kindle unlimited is such a nice service.  Given that I’m happy to consume 2 books while on the treadmill before work, and at least one before bed .. every day, I’d call this a losing proposition for them.

For me it’s very much like being left unattended in a candy shop.

Spring upgrades

Well, it’s still january, but it was warm today, so that counts as spring right?

Ordered the upgrade for my primary workstation.  I’ll migrate the current primary down to my secondary, and put the current secondary away until it’s needed.

It’s been about 18 months or so since I upgraded, so I’m about due. I likely won’t need to upgrade again for another 3 years however, as this system won’t become obsolete any time soon.

It’ll be a week or two until it arrives, and another week or so until I do the switchup.

Haproxy means never needing to say “oh yeah, port”

After a not insignificant amount of time, I finally figured out how to use ingress controllers with Kubernetes. What this meant in the short term was no longer having to use NodePort entries, which map one service to one port (usually above 30000).  Nope, now http(s) services could all run through a single gate (or ingress, as it’s aptly named).

Finally working, I had an http ingress set up on port 30500, and it has been working really well. Kubernetes will not run exposed services on anything outside of the 30k port range, so I kept having to add :30500 to all of my entries.

Tonight I added haproxy on the kubernetes hosts, which maps 80 to 30500.  Unsurprisingly, it works beautifully.  Now I can run to that instead if I so choose, and only use 30500 when I’m diagnosing things.

Progress!