О граблях в архитектуре баз данных
Привет, Хабр! В предыдущей статье мы говорили о тех ошибках, которые допускают начинающие администраторы при работе с PostgreSQL. А сейчас мы рассмотрим те грабли, на которые могут наступить начинающие архитекторы при построении структуры баз данных. Начнем с первичных ключей.
Scott McAllister presents on E2E Testing July 24th at Nebraska.Code().
Why I went all-in on GitOps for my AI infra stack
Amazon EKS. Docker, Terraform. Argo CD. HashiCorp Vault.
Zero manual steps. One terraform apply.
Watch how it all connects:
https://youtube.com/shorts/IbLynm1S66I
DevOps is evolving. GitOps is the new standard.
No more “who broke prod?”
Clean PRs
Instant rollbacks
Total control
If you're serious about infra, watch this:
youtube.com/shorts/qKWWS2Uyb4w
How I built a production-grade GitOps pipeline on AWS
Docker,
EKS,
ArgoCD,
Vault,
Terraform — all in one CI/CD flow.
No fluff. Just real-world DevOps that scales.
Watch here: https://youtu.be/PpEfaQq2Umk
LLMs aren’t magic.
They run on containers , CI/CD
, and GitOps
.
The real flex?
Infra that just works behind the scenes.
Watch the Short: https://youtube.com/shorts/f2vAS6i1kuQ
#Kubernetes is more than a containerized app platform: it can provide better database management and automation for your business without vendor lock-in.
Learn how you can set up a #postgreSQL kubernetes cluster and manage anomalies to keep your organization’s databases running smoothly and cost-effectively in the #cloudnative world:
Free ArgoCD Up & Running eBook (Early Release)
Learn how to manage Kubernetes clusters and application configurations with Argo CD, the easy-to-use open source GitOps engine.
Sponsored by Akuity
Download from here: https://landing.akuity.io/resources/argo-cd-up-and-running
#argocd #kubernetes #gitops
Okay, authentik is up! Took a while, I was fighting against flux and the helm release because it deployed with the wrong StorageClass (I forgot to have that configuration ready before release.) Helm wasn't able to modify the PVC because they're immutable, updating the release has to wait for the initial release to succeed (which it won't) or timeout and flux is quiet on the reasons for all of this unless you know where to look lots of learning was had though!
Anyway, admin and personal user accounts created, MFA enabled. Got my first application integrated too! (actual budget)
What next? The world is my oyster... Probably gitea or semaphore. I'm hesitant to integrate services like jellyfin before I have more users onboarded and this gives me an opportunity to experiment with other edge cases like other providers and service accounts and such
Interesting piece on the details of actual scale and shifting from Helm to CueLang with ArgoCD. Includes the why's as well as lessons learned.
Anyone using terraform/opentofu for their homelab setups? Either on infra level or for CM?
I've made it a project for this year to get everything managed via gitops. I'm taking it step by step and as such I haven't locked down manual write access so that I can tinker with stuff and troubleshoot as needed.
I'm finding that I need a good way to spot state drift so that I get notified if I forget to correct things afterwards. I think this is going to be less frustrating than fighting against enforced state while I get my bearings.
I guess I could use a cron or a timer unit. Unless someone has any recommendations? I would like to manage all the TF using fluxcd eventually but I think it's too early to start enforcing desired state right now. I'm open to suggestions...?
Et si l'on vous disait que le #GitOps, ce n'est pas que mettre dans #Git ce que vous déployez, mais aussi une philosophie et des concepts!
J'aurai l'honneur de vous en parler à @devoxxfr 2025!
Et pour m'accompagner, le plus mignons de tous les robots ! #astro
https://link.davinkevin.fr/AstroGitOps-devoxxfr25-program
Si vous avez des questions et/ou des retours d'expériences, n'hésitez pas à me pinger !
Et n'oubliez pas de mettre la prez dans vos fav ️
My favorite thing about gitops is making noop white space changes to the code to get the gitops thing to redo the thing is supposed to have already done.
The week and the month is ending so abruptly. No time left for to test on staging and UIT. Gonna just deploy to prod in a Friday and call it a day :-)
git config user.name "BOFH" && git merge main && git push --force && shutdown -h now