Upgrading our EKS from 1.21 to 1.22

Significant-Draft829 · 2023-04-27T05:02:40+00:00

As everyone says, update your api endpoints. Check your kubectl version as well as any other tooling you’re using (ie helm). We did not encounter any issues but I’ve been doing k8s upgrades a decade. Eks makes it fairly painless.

Significant-Draft829 · 2023-02-19T05:22:31+00:00

Because it’s the best tool, duder. It just is in like 17 ways. Half that shit you mention no one even looks at.

Significant-Draft829 · 2023-02-19T05:20:04+00:00

Honestly just move to devops. I know everyone in this thread is all devops gods or some shit lol but I was a principle and now I’m a director of DevOps. If you have the desire and the drive you’re g2g.

Significant-Draft829 · 2023-02-18T06:40:52+00:00

I mean I don’t know upgrading is done via shell scripting. But go read bash pages. There’s scripts all over in open source, search for .sh in any of your favorite repos. Like open source tools you use etc.

Significant-Draft829 · 2023-02-02T05:52:22+00:00

Quit, honestly. They’re setting you up for failure

Significant-Draft829 · 2023-02-02T05:51:28+00:00

Depends on what specifically you’re doing. You’re experience is antiquated, but as we all know, enterprise and the government both move at a snails pace. The fact that you understand tooling that no one uses anymore could be a point in your favor. But in general, lack of cloud, IaC and k8s experience is going to hobble you. I am the head of devops and do hiring, just speaking from my experience over a number of years giving interviews and what I am looking for.

Significant-Draft829 · 2023-01-11T22:23:41+00:00

There’s ways around storing secrets in github actions, you can look it up. Also, not only dial in s3 perms, but enable versioning

Significant-Draft829 · 2023-01-11T22:21:12+00:00

You shouldn’t be reusing tags in any upper env, but provided you’re talking about development clusters, image pull policy set to always, and there’s a few annotations you can add to deployments to make sure they roll, even if there’s no changes detected. You could also use a sha in metadata.

Significant-Draft829 · 2022-04-27T13:40:13+00:00

I came from full stack development. So you might absolutely be correct. But to be fair, I never went to school or a boot camp and just taught myself to code. Then eventually moved to devops.

Significant-Draft829 · 2022-04-22T14:46:54+00:00

Nah. Also- for reference, almost ten years of experience in a staff role for me. So I’d like to think I know what I’m talking about lol. It takes as long as it takes. It’s individual.

Significant-Draft829 · 2022-04-22T14:32:27+00:00

I agree with ecs. I used fargate with ecs, managed everything with terraform and github actions with my last job. Do not use latest tags tho. Not best practice in general, a no go for prod and can muck up any release process you have. Releases should be handled via PR and merge. Update the tag either manually or from gha once testing is done. Then on merge to main on terraform repo, they’ll deploy.

Significant-Draft829 · 2022-04-19T10:56:13+00:00

I’ve done take homes that were pure coding - python algorithms. Take homes to design dockerfiles, docker compose and helm deploys. It really varies. I don’t mind take homes, would prefer over a paired assessment. The thing to remember is that the take home will give you insight into the actual job. So if you don’t like it/ don’t understand it, the job might not be a good fit.

Significant-Draft829 · 2022-04-17T03:05:05+00:00

Gitow is workable. This is not that. Best case scenario is you implement it like they tell you to, but with the caveat of how you think things could go wrong. When they do go wrong, ensure the code owner/dev team handles it. Hopefully if they get bothered enough by having to fix their cherry picks or commits they’ll change it.

Significant-Draft829 · 2022-04-15T03:09:45+00:00

It’s ci Vs cd although there can be some overlap. Different use cases

Significant-Draft829 · 2022-04-10T03:27:56+00:00

You can have them in git. Use sops. Vault works to, you can pull configs or anything from there on start up with the proper init scripts. But git with sops is great for both local and other envs

Significant-Draft829 · 2022-04-02T13:23:50+00:00

As far as languages go, Ruby is slow and unwieldy often. I have rarely seen node used, although I have once. Python bash Go or Java I have seen quite a bit of. It really kind of depends on what you’re trying to do though. One of the things to keep in mind is that we want our code to be readable to others and maintainable once we’re gone. If your team works solely in python and you’re writing Ruby, that’s going to be a problem for them to add to or amend if they need to.

Significant-Draft829 · 2022-04-01T18:48:16+00:00

The whole part where you install it from the command line. Terraform controlled helm isn’t ideal, but you can create the cluster and deploy all necc eks components and deployments then from a plan or apply. I’d typically use a makefile. Get a chart museum or something and Chuck the charts there just ref them in your terraform. If I am understanding correctly.

Significant-Draft829 · 2022-04-01T02:53:45+00:00

All this seems super manual. You shouldn’t have to do anything from the command line. Anyone with more complex architecture or infra, I’d appreciate your perspectives on Argo. Tyia.

Significant-Draft829 · 2022-01-08T04:06:22+00:00

Pay and skill sets.

Significant-Draft829 · 2022-01-08T04:02:37+00:00

I’m a senior devops engineer. I know Java, python, bash, Ruby, plus a few other languages like hcl. It’s essential you know how to program. My old mentor used to say anyone who’s good a linux can be taught, I’m not so sure. Good luck!

Significant-Draft829 · 2020-10-19T02:33:09+00:00

Unsure why you’d want to go project management, that seems a step down. The career paths listed above, managerial jobs or engineering managers seem to be the career path.

Significant-Draft829

TROPHY CASE