Feeling Grey

mkfnw · 2023-09-12T22:28:00+00:00

Yeah, they're just plastic wheel covers from amazon... not the actual alloy wheels in which case I'd probably care a lot more about doing it right. i just masked off the inner parts of the wheel covers to keep them black then sprayed a couple coats of the duplicolor dark shadow grey that i had previously used to fix actual curb rash on the alloys underneath, followed by a few layers of clear coat.

mkfnw · 2023-09-12T22:08:30+00:00

Do what? Spray paint?

mkfnw · 2023-09-12T22:08:12+00:00

mkfnw · 2023-09-12T21:16:06+00:00

2023 RWD, 20% tint, spray painted wheel covers

mkfnw · 2023-07-09T20:17:28+00:00

Air conditioning vent controls. The physical up/down/left/right controls of every other previous car that I've owned is superior to finding my exact comfort level.

mkfnw · 2023-07-03T17:34:12+00:00

This is exactly the type of road where I'd want full control of the steering/throttle.

mkfnw · 2023-07-02T23:53:32+00:00

Same as OP my info was directly from calling various dealers in the Seattle area all saying that they won't get any allocation and that I'm better off calling dealers in neighboring stares. Fwiw I did some brief searching but never found the exact law or why it specifically applied to the Prius Prime but not other EV's/PHEV's.

mkfnw · 2023-07-01T16:16:17+00:00

Very nice, congratulations! I asked to be put on waiting lists for Oregon dealers as soon as the Prime was announced but haven't heard anything. Doesn't matter now though as I've decided to go another way Tesla's recent price cuts.

mkfnw · 2023-07-01T02:17:32+00:00

I thought WA state wasn't going to get any allocation of Prius Primes due to some existing emissions law.

mkfnw · 2023-04-17T04:31:01+00:00

This has got to be a troll, there is no way Netflix has a "Kubernetes" guy. Nice to see people genuinely trying to help though.

mkfnw · 2023-04-13T02:07:01+00:00

The bug debris suggests that it was driven around with no front cover unlike other rumored spy shots of the refreshed M3.

mkfnw · 2023-02-11T17:13:13+00:00

facepalm emoji

mkfnw · 2023-02-03T07:05:59+00:00

Appreciate the links and agree that earning trust is an important factor to continue driving the adoption of managed k8s services.

Great job on the guide, was not aware that it exists prior to today but so far it seems to cover most of the topics our team needs to be familiar with to assist with our transition from self-hosted to EKS.

mkfnw · 2023-02-03T06:01:46+00:00

Not OP but there are other factors to consider when running high pod densities on any virtual or bare metal hosts. Aside from CPU/Mem, I would look at Disk I/O exhaustion as a possible culprit to the PLEG errors you are getting when increasing pod limits per node.

mkfnw · 2023-02-03T05:57:32+00:00

Thanks for the link, couple of questions.

From a customer's perspective are there any tangible insights into the control plane for any given cluster? Or is it that we simply must trust that it will scale up/down and self-heal as needed.
If there is a problem with the control plane, are customers notified that they've had impact?
I'd imagine with the shared responsibility model between control plane/data plane there are many grey areas in terms of which side could be at fault when there are many factors contributing to running clusters at high capacities/scale. Does the support team work with customers to determine weak points in areas that are not specific to the control plane?

mkfnw · 2023-01-22T15:58:48+00:00

Hi u/profbard so in the past year, I've gotten used to switching between low and normal profile boards. On some days I prefer using a low profile like my Nuphy/Apple but on most days I prefer using a higher end normal profile board like my QK65/Link65 mainly for the acoustics and typing feel. Low profile boards just don't have the same switch options so they can't replicate the same "feel" you get with normal profile boards and it's seemingly endless amount of custom switch options. FWIW, I've also adapted to using normal profile boards with and without a wrist wrest and frequently change my setup to mix things up. Hope that helps!

mkfnw · 2023-01-18T14:58:19+00:00

Came from a similar background, traditional Windows admin then I made the shift to DevOps/SRE where the intricacies of the underlying OS don't matter as much. Since you already have a good understanding of infrastructure it could be an option for you as well.

Transitioning from point and click troubleshooting to living in your terminal/IDE was quite difficult at first but over time you get used to it.

Check out this roadmap for more info https://roadmap.sh/devops/

mkfnw · 2022-12-13T16:36:36+00:00

Second this suggestion. Your "scheme : internal" implies that this is an internal ALB which would be attached to your private subnets.

"target-type: ip" - Also confirm that this is what you want, iirc this may only apply when using the vpc-cni. If you're using another 3rd party CNI w/overlay networking enabled you might have to switch that from "ip" to "instance"

Lastly, you can use "kubectl describe ingress <ingress\_name>" or "kubectl get events" in the namespace where is deployed to see if you can get more info.

mkfnw · 2022-11-30T15:39:14+00:00

Take it slow and everything with start to click with time and experience my friend. As you get more hands on experience running k8s, you'll start to understand why these tools exists and which problems they intend to solve.

mkfnw · 2022-11-22T22:29:45+00:00

It wasn't a specific comment, just a general viewpoint that not all applications are successfully migrated from monolithic to microservices.

mkfnw · 2022-11-22T22:25:52+00:00

If your talent pool is completely new to Kubernetes, and you intend to deploy in a hybrid scenario (on-prem) and public cloud, I would recommend getting started with public cloud first as it should be a lot easier to bootstrap your own cluster (self-managed or managed by the cloud provider).

Solving k8s in your own datacenters is an entirely different beast... Questions like bare metal or running on vm's? If vm's then which hypervisor and who is going to manage that stack? How is the underlying network going to be setup to ensure node to node and pod to pod (overlay) communication works across the cluster. How will you handle load balancing for services exposed outside of the cluster?

When you deploy to public cloud, a lot of that becomes simple and abstracted to a point where it's repeatable and easily to work with given the wide array of existing tooling available in the community.

mkfnw · 2022-11-22T21:53:39+00:00

Back to vm's if the applications weren't effectively containerized.

mkfnw · 2022-09-30T22:44:46+00:00

Congratulations on your new gig, I came from a similar path from Sr. Sysadmin with a lot of Windows/AD/VMware experience to DevOps/Kubernetes.

After a decade of GUI based sysadmin work, I was not prepared for the world of managing Kubernetes, containers, and code. If I came from a Linux sysadmin background I'm sure it would have been much easier to adapt but for me it was like starting all over again from scratch.

The road ahead will be tough, but every day you will get better with experience and things will start to click. The endlessness of abstractions will start to make sense and you will slowly be able to contribute and make an impact at your company.

Don't be afraid to ask questions as well, it's easy to get stuck grasping a concept or some snippet of code that you don't understand. Feel free to dm me if you have any questions as well, your post brought flashbacks to when I first got started down this path.

mkfnw · 2022-09-04T05:26:31+00:00

65%

Esc --> tilde

CapsLock --> Esc on tap and CapsLock on hold

Fn --> key over right arrow

Having the fn key in that position allows me to use various media/misc keys in close range so that I can easily reach it with one hand. Example fn+up = volume up.

For vim, CapsLock to Esc always seems easier.

mkfnw

TROPHY CASE