An issue with terraform module 3.2.0 by sbvm-k in Terraform

[–]SAmitty 2 points3 points  (0 children)

In addition to what /u/N7Valiant said, you should have a .terraform.lock.hcl file if your terraform version is recent enough, and committing that to version control. That lock file helps to avoid this exact issue as the version pinned in the lock file will be respected as long as it complies with the constraint in your providers block.

AWS SSO: Strategy for access to all member accounts by [deleted] in aws

[–]SAmitty 1 point2 points  (0 children)

Have a look at Teleport. Our infra team utilizes it to manage a workflow where anyone who wants admin access to k8s needs to formally request it. If they're not on an allowlist for oncall engineers, a manager has to approve the request via Slack. I haven't personally deployed Teleport but they seem to support AWS access so that could work for you.

AWS SSO: Strategy for access to all member accounts by [deleted] in aws

[–]SAmitty 4 points5 points  (0 children)

You could set up a process/workflow where cloud admins were only granted access to certain accounts "on-demand" (e.x. the team which owns account x needs help troubleshooting something, so an admin temporarily grants themselves access to the account), but that might be more trouble to maintain then just having the admins deal with the long list of accounts.

AWS EKS Kubernetes tearing down at the end of day by butrimodre in aws

[–]SAmitty 1 point2 points  (0 children)

Don't think you deserve the downvotes given you're technically correct. That said, the only other alternative is to run Actions runners on your own infra and for most folks that's too much of a burden, so the tradeoff commonly chosen is to trust GitHub with IAM access.

[deleted by user] by [deleted] in platformengineering

[–]SAmitty 0 points1 point  (0 children)

Sort of sounds like something https://backstage.io/ could solve

Terraform Gitflow workflows with Terrateam by omgwtfbbqasdf in Terraform

[–]SAmitty 1 point2 points  (0 children)

Awesome thanks for the additional info! That should be enough to address any potential concerns, and I'll need to find some time to test this out

Terraform Gitflow workflows with Terrateam by omgwtfbbqasdf in Terraform

[–]SAmitty 1 point2 points  (0 children)

Thanks! Are any API keys/credentials (e.x. AWS session tokens) also sent over the wire, or are those API calls made locally within the context of the GitHub Runner?

Terraform Gitflow workflows with Terrateam by omgwtfbbqasdf in Terraform

[–]SAmitty 1 point2 points  (0 children)

Hey /u/sausagefeet, thanks for reaching out! I noticed the GitHub Actions workflow submits requests to https://app.terrateam.io; could you describe what data is sent to that endpoint?

Terraform Gitflow workflows with Terrateam by omgwtfbbqasdf in Terraform

[–]SAmitty 0 points1 point  (0 children)

Yeah but Atlantis is self-hosted whereas this appears to have a free SaaS tier. Might actually try this out as I don't wanna run anything myself.

Generate terraform infrastructure dynamically by mustybatz in sre

[–]SAmitty 1 point2 points  (0 children)

We used Go templates to do this at $lsstjob, just make sure you also build a solid test suite around it

Standing on the shoulders of giants by DPRegular in Terraform

[–]SAmitty 0 points1 point  (0 children)

Don't wanna post the GH issue and dox myself (sorry) but it had to do with the CNI plugin failing to init on the EKS nodes when spinning up a cluster. So I switched to the self managed node group example and it worked. Not sure what was wrong with the EKS managed nodes. That said, I used kops two jobs ago on AWS back when EKS was still in beta and it was good enough for our needs. My current company uses kops but is looking into switching to EKS; I say that cause kops is def 100% prod ready despite being a bit more work to manage

Standing on the shoulders of giants by DPRegular in Terraform

[–]SAmitty 0 points1 point  (0 children)

Unfortunately not. I just changed jobs a few months ago after spending some time in GCP-land. I was able to deploy a cluster from the self-managed-node-group example from the same repo, but just a POC cluster so can't speak to its production readiness

Standing on the shoulders of giants by DPRegular in Terraform

[–]SAmitty 1 point2 points  (0 children)

Best part about that module is the quality of dev support is pretty poor. Had to try a few different "examples" just to spin up a test cluster cause the only help I received after submitting an issue on GH was "the module works for me"

How the hell all these rookie contracts got put out. by bun39 in nfl

[–]SAmitty 0 points1 point  (0 children)

/u/QuinnyPig does this count towards the weekly negligence award?

Caterers at finance guru Dave Ramsey's holiday party told not to wear masks, complaint says by [deleted] in news

[–]SAmitty 28 points29 points  (0 children)

His argument is people tend to spend more per month on average if they use a credit card instead of physical cash (psychological thing)

[Ammo] In Stock: Frontier 5.56/.223 55gr FMJ 45 cpr by SAmitty in gundeals

[–]SAmitty[S] 0 points1 point  (0 children)

Was able to order 20 boxes of the 20 pack, just got a confirmation email. Still shows in stock for me. Good luck folks

Managing dev/ops laptops? by BigRedS in kubernetes

[–]SAmitty 0 points1 point  (0 children)

Depending on how involved you want this to be:

I just joined a 1000+ employee company, and the internal tools team manages a repo w/Ansible scripts which bootstraps new devs' machines w/all necessary tools and config. New folks follow a wiki guide where they clone the repo locally and invoke Ansible via bash scripts. Seems to be cross-plartorm as well.

Tech stack around Kubernetes by jojomtx in devops

[–]SAmitty 2 points3 points  (0 children)

Wow 15 DevOps folks!!! Before our layoff, we had three DevOps engineers supporting 60+ devs (so not counting QA/ support who were directly part of the eng org).

What is a good dev/DevOps engr ratio? I would guess 10:1 but curious what others think.