1

I'm lost in the forest of GitOps / DevOps with k8s deployment

I find information on

  • Infrastructure as Code (Terraform)
  • Kubernetes k8s cluster, all the k8s manifest, Docker Container
  • Flux

but it's not clear how these tie together.

Is there recommended reading on the big picture? I wasn't successful in finding a hello world e2e pipeline which shows the deployment Gitlab-IaC-(AWS/GCP/...)-k8s-WebApp, probably you know something?

Harsh Manvar
  • 27,020
  • 6
  • 48
  • 102
til
  • 832
  • 11
  • 27
  • any update on this ? feel free to update the status of question if below answer resolves your issue. – Harsh Manvar Apr 26 '23 at 11:52
  • This is a broad question topic, with several answers that depend on your experiences. Can you probably narrow the question down? Or feel free to pung me via PM to help you to sort it out. – aholbreich Jun 18 '23 at 16:13

1 Answers1

0

You can refer to my Github which has very normal basic GitOps terraform to provision the GCP instance.

It could be different as you can have multiple repos storing the configs of Gitlab CI and you can important it another repo like modules.

Generally, Infra(Terraform) and App(Helm, K8s YAML) deployment will be in different repositories so both have separate Gitlab CI config and workflow.

This is not the Gitops example but it's CI/CD with GCP cloudbuild will give you idea you can write the gitlab-ci.yml

Server.js is normally code get docker build when commit occur to Gitrepo and there is another trigger config file when you run that it updates deployment.yaml file with sed command set the Image and apply the config file.

Harsh Manvar
  • 27,020
  • 6
  • 48
  • 102
  • the examples look reasonable but very hard to get a quick understanding. If you probably could add more insights to its readme, that would help. – til Jun 19 '23 at 07:51