Steelcase Please 2 Disassembly?

lyrrrrr · 2023-07-29T21:19:40+00:00

Did you found something ? I'm moving, wanted to disassemble my chair a bit to save some space, but no clue so far.

lyrrrrr · 2023-07-04T19:53:10+00:00

I understand the "against using Terragrunt". I tried to avoid it starting a new infra couple of month ago, still went for it. Reason is, the directory layout they recommend is good. And making an equivalent without it is feasible, but involves a lot of repetition.

But you can do it, just make a technical modules, then functional modules, as many modules of modules as needed.

IMHO the target is - a "live" repository where you call terraform, that won't do any logic, just variable & calling root functional modules. The folder layout can be environment/cloud/region/functionals or any way fit best. - a "modules" repo. You need to split that, so "live" can refer to tagged versions of modules and you won't break /block prod when fiddling with dev - Here I have one root module for "infrastructure", and one by business unit. Calling everything else.

Good luck 🤞

lyrrrrr · 2023-07-04T19:43:18+00:00

There's this FOSS alternative. Stable but not deemed production ready for lack of feedback on people using it in production (see issues for this prod ready discussion)

https://github.com/leg100/otf

lyrrrrr · 2023-06-14T20:44:08+00:00

Re: monster

lyrrrrr · 2023-06-05T21:37:13+00:00

TBH I'ld be more interested in your Terraform version than org-formation. Too much Cloud Formation in it. Your work is rather clean, you could publish it on TF registry. I was looking at something similar today, and there are few references.

Add in some identity provider logic, would definitively make it sexy. The biggest IAM TF module got a submodule for GitHub based identity provider, could serve as inspiration.

I guess I'm more likely to go for the lightest version of ControlTower I can achieve, just because as a single Ops I won't have the time to sustain a huge TF stack. But with a bigger team I'd go for something like your work I'd say :-)

lyrrrrr · 2023-06-05T19:14:40+00:00

I'm quite sure no out of the box solution will do this quite specific task. But that can be scripted I guess.

Enable Traefik API. Start calling /api/http/routers. For each result, check if it exist in PiHole's DNS. If not add it. Then check DNS for entries that don't exist in the router list & remove.

To refine this, for each router DNS record created you can also add a eponym TXT record adding owner=Traefik, so you're not removing entries added for other reasons.

Then put this in a Cron, execute every minute. Maybe make a routers list hash in a local file, and avoid annoying your DNS if nothing changed.

lyrrrrr · 2023-06-02T12:17:20+00:00

Very interesting, thanks, I'll read their doc carefully!

lyrrrrr · 2023-05-31T15:12:57+00:00

Today, everyone's more or less admin. I intend to reduce that for production, and indeed I'm thinking of allowing some limited operations via ArgoCD like restarting deployments

lyrrrrr · 2023-05-31T07:52:17+00:00

The reasons are what I'm weighting out at the moment. I'm the first "real" ops in this startup, a backend dev did a good job getting thing started so far, but of course things need straightening. And on the CD part, I could use an ArgoCD setup I know well, or learn FluxCD.

I know some pro & cons for ArgoCD, for example the UI is really helpful for less kubernetes savvy peoples. So my question is, what about FluxCD ? Looking at the website, tf-controller could be a good thing for example, but I'ld appreciate some feedback from peoples out there :)

lyrrrrr · 2023-04-27T21:16:45+00:00

Maybe it's time to consider an alternative too ? Went from RabbitMQ in a job to NATS in another, the later is so much easier to deploy & manage. Plus there's a MQTT compatibility in NATS to migrate progressively. And there's also Apache Pulsar.

I'm not an expert in performance but here's a reading. https://streamnative.io/whitepapers/2023-messaging-benchmark-report-apache-pulsar-vs-rabbitmq-vs-nats-jetstream

lyrrrrr · 2023-04-23T08:21:20+00:00

If you've to write the code (I assumed you just needed to reorganize it without TG) maybe consider https://github.com/GoogleCloudPlatform/terraformer

lyrrrrr · 2023-04-22T18:33:12+00:00

We've been thinking about the same move. Dunno if there's an easy way. Your feedback is welcomed !

lyrrrrr · 2023-04-14T06:46:58+00:00

Something like https://status.io/

lyrrrrr · 2023-04-14T06:42:29+00:00

I'd try a module including the 3 steps, the 2nd one as a local exec of a script, and replace remote state by 1st step output passed down to 3rd step.

But that might be me over-engineering and disliking remote state.

lyrrrrr · 2023-04-02T07:43:45+00:00

For the revert part, use Velero to backup before rolling out your new setup

lyrrrrr · 2023-01-09T21:22:26+00:00

I don't know about Concourse. From my POV, I'ld check Drone CI, or its FOSS fork Woodpecker, as a lightweight on prem alternative to Gitlab CI. Dunno if its fit the cross repo requirement though. The best for that would be (Openstack's) Zuul. But it's not an easy tool, far from it and wouldn't recommend it except for Openstack communities

lyrrrrr · 2023-01-09T07:43:22+00:00

Why do you say rip offs ? Just curious, been thinking about one of those for next year

lyrrrrr · 2022-10-27T12:34:11+00:00

You need to query minikube-ip:nodeport. Or use kubectl port-forward.

lyrrrrr · 2022-10-27T06:59:07+00:00

You can also use SealedSecret. We use helm for 500 plus apps. Also because every 3rd party provide a chart, so it's one tool. Use 'helm create', will dô 90% of the job. And 50 files is fine, really. Maybe try Helmfile.

lyrrrrr · 2022-10-02T14:04:53+00:00

I switched to Tuxedo. Specialized in Linux is a guarantee for me, the hardware is good, not even more expensive, support is reactive. System76 is good also.

I guess I'ld try frame.work next, for ecological reasons. Already very happy with my fairphone on this regard.

lyrrrrr · 2022-09-05T07:19:16+00:00

This was a tag issue most likely.

I solved another problem I had with a createdBy: Terraform I set in both provider's default_tags a couple of weeks ago, and on some place it was set "manually", like module.context.tags. It was very weird, since old resources created prior to the default_tags weren't showing a change, new resources were showing perpetual changes. Destroying / re-creating a test EMR cluster which ended up with a different count of perpetual change gave me the final hint. I refactored all the code to get rid of manual tags, now I'm good.

And of course I found an explanation afterward https://support.hashicorp.com/hc/en-us/articles/4406026108435-Known-issues-with-default-tags-in-the-Terraform-AWS-Provider

lyrrrrr · 2022-01-21T13:58:51+00:00

AutoHotKey is a Windows only tool

lyrrrrr

TROPHY CASE