5 ms·

Serious question: How do organizations deal with having git on the critical path for deployment? Current employer actually prohibits this due to frequent outa

Serious question: How do organizations deal with having git on the critical path for deployment? Current employer actually prohibits this due to frequent outages in the git plant.

numbsafari 9mo ago
Ummm … github is not git … if you must, keep your git stored locally and simply use webhooks to keep it synced whenever changes are merged via your forge of choice… you can, if necessary, make updates to your locally hosted repo in the event of an outage at the forge, but you’ll need a procedure to “sync back” any changes made during the outage. Fortunately, the whole thing is git based, so you have all the tools you need to do it.
grayhatter 9mo ago
> Current employer actually prohibits this due to frequent outages in the git plant. Even without knowing what you mean by git plant. I can tell you you're holding it wrong. I'd like to help, but I can't offer useful suggestions if I have no idea what you're even doing, or prohibiting.
calgoo 9mo ago
gitlab on internal network works quite well. You can still use K8 / EKS / AKS for runners etc, just run it all on the internal network. Im always surprised at how many orgs use public platforms for their code and ci/cd.
master_crab 9mo ago
Git is just the repo store. Everything you are referring to is the CI/CD pipeline. GitHub actions, Gitlab Runners, ArgoCD; they can all do some sort of gitops. Those dependencies existed before gitops anyway, so nothing new is being added.
locknitpicker 9mo ago
> Serious question: How do organizations deal with having git on the critical path for deployment? You mean like storing source code? CICD pipeline definitions? Container image specs? IaC manifests? Service configuration files? I don't think that arbitrarily drawing the line on what package version is being deployed is a rational opinion to have. I mean, look at npm's package.json. Is it ok to specify which dependency versions you bundle with your software, but specifying which version you're deploying is unheard of? The only drawback I see in GitOps is that CICD pipelines are still lagging way behind on providing adequate visualization strategies to monitor the current state of multi-environment deployments.
cortesoft 9mo ago
We use flux for our gitops, and it is easy to bypass if we need to in an emergency. You can disable reconciliation and then manually apply a change if your git repo is unavailable.
antonvs 9mo ago
> frequent outages in the git plant. What are you talking about. And whatever it is, it’s wrong.

Serious question: How do organizations deal with having git on the critical path for deployment? Current employer actually prohibits this due to frequent outages in the git plant.

numbsafari 9mo ago

Ummm … github is not git … if you must, keep your git stored locally and simply use webhooks to keep it synced whenever changes are merged via your forge of choice… you can, if necessary, make updates to your locally hosted repo in the event of an outage at the forge, but you’ll need a procedure to “sync back” any changes made during the outage. Fortunately, the whole thing is git based, so you have all the tools you need to do it.

grayhatter 9mo ago

> Current employer actually prohibits this due to frequent outages in the git plant. Even without knowing what you mean by git plant. I can tell you you're holding it wrong. I'd like to help, but I can't offer useful suggestions if I have no idea what you're even doing, or prohibiting.

calgoo 9mo ago

gitlab on internal network works quite well. You can still use K8 / EKS / AKS for runners etc, just run it all on the internal network. Im always surprised at how many orgs use public platforms for their code and ci/cd.

master_crab 9mo ago

Git is just the repo store. Everything you are referring to is the CI/CD pipeline. GitHub actions, Gitlab Runners, ArgoCD; they can all do some sort of gitops. Those dependencies existed before gitops anyway, so nothing new is being added.

locknitpicker 9mo ago

> Serious question: How do organizations deal with having git on the critical path for deployment? You mean like storing source code? CICD pipeline definitions? Container image specs? IaC manifests? Service configuration files? I don't think that arbitrarily drawing the line on what package version is being deployed is a rational opinion to have. I mean, look at npm's package.json. Is it ok to specify which dependency versions you bundle with your software, but specifying which version you're deploying is unheard of? The only drawback I see in GitOps is that CICD pipelines are still lagging way behind on providing adequate visualization strategies to monitor the current state of multi-environment deployments.

cortesoft 9mo ago

We use flux for our gitops, and it is easy to bypass if we need to in an emergency. You can disable reconciliation and then manually apply a change if your git repo is unavailable.

antonvs 9mo ago

> frequent outages in the git plant. What are you talking about. And whatever it is, it’s wrong.