How do you manage dependencies and ordering of resources managed by Kubernetes?

@andreaspoly

6 ай бұрын

ArgoCD with sync and waves 🎉

@juanbreinlinger

6 ай бұрын

Helm + taskfiles with built in dependencies and outputs (Similar to gradle tasks)

@matteobaiguini5940

6 ай бұрын

ArgoCD rules for whatever is not offered by K8s out of the box

@matteobaiguini5940

6 ай бұрын

anyway following GitOps it's right way to go... using ArgoCD sync-waves is just a little trick to deploy and let things work faster, avoiding many failures in the loop...

@jacekbartyzel2106

6 ай бұрын

Argocd sync waves + hook jobs in sync phase in specific sync wave that validate if dependency is satisfied before progressing the sync. For example you install the operator and then in next sync wave run a hook job that validates if CRD was already created. Script validating if CRD exits with 0 if CRD is there or it exits with 1 and sleeps for 120 seconds. In job you set backofflimit to 15 and now you have gate that will check for 30 minutes if CRD was created. Once it is there you sync your custom resource. Quite handy pattern. I used for whole day2 Openshift setups, like moving ingress routers to infra nodes after Infra nodes have finished installing, but sky is the limit here 😊

Thanks for another great video 🎉 honestly I was waiting for one on this subject, app dependencies can be tricky if not done the right way and at the beginning of my kubernetes journey I was struggling with them too! I took the path of remote development and luckily I solved many problems with it, but I still think the subject is worth a clarification

The hard part about eventually consistency is that in a complex system it can take a while for the system as whole to reconcile and while waiting it is hard to tell how far along the system is, is it stuck in an crash loop, why is it stuck in the spot it is stuck in ... etc. So tools that support ordering or troubleshooting are very useful the larger the system gets. A constraint based approach can also be very helpful.

@DevOpsToolkit

6 ай бұрын

It's true that troubleshooting a complex system is difficult, but so is the imperative orchestration.

@AdibSaikali

6 ай бұрын

You don't need to get to imperative orchestration to get the ordering required. A query and constraints that must be true before the next set of objects to start reconciling can do the trick. So you don't write a sequence of step1, step2, step 3 rather you say something like a pre-req for this object to start reconciling is a that a query result set meets certain criteria. This allows the reconciler to figure out what things can go in parallel and what waits until certain conditions are true ... etc. Canary rollouts use this approach where they wait until a query against a metrics store meets some condition before proceeding to change the desired state. I really wish the k8s API server had a native feature that allowed objects to be accepted but does not start reconciling until a query condition is true, its is just the flip side of being in a crashloop backoff, but at least you would see something like waiting for x condition to be true to start reconciling. makes troubleshooting a lot easier.

@DevOpsToolkit

6 ай бұрын

@AdibSaikali that's similar to what i tried to expñain except that I used data as a dependency instead of a query. If data required to create a resource is available, more often than not, there is no impediment to create it.

Great video, man! I'm interested on the second part, about deletion, in case you're willing to record it :-)

@DevOpsToolkit

6 ай бұрын

Great. I'll start working on it soon.

@user-ts8yn8zd1v

6 ай бұрын

@@DevOpsToolkit Also looking forward to the follow up on destruction. The current video is my pointer to get colleagues up to speed about this eventual consistency model of deploying.

Completely agreed on all points!

Great talk again today. Again, the bubble sounds distract. Would love to have seen an animation, and/or code/config example of the process as you've articulated it.

@DevOpsToolkit

6 ай бұрын

I'll work on a video with hands-on variation.

@frost266

6 ай бұрын

For feedback, I quite like the 'bubble' sounds, they help punctuate milestones in your communication.@@DevOpsToolkit

19:55 this sounds very similar to: KPT says "configuration as data"

@DevOpsToolkit

5 ай бұрын

KPR is running on client-side so the functions will be executed only once and that means that you have to run them in certain order.

@autohmae

5 ай бұрын

@@DevOpsToolkit Seems I put in the wrong timestamp, I meant 19:30 you mentioned it's all data, I was just pointing out, KPT calls it data too.

@DevOpsToolkit

5 ай бұрын

@@autohmae Oh yeah. From the data perspective, KPT got it right.

How can we define the deployment order&dependencies in argocd? Any ideas?

@DevOpsToolkit

6 ай бұрын

Take a look at kzread.info/dash/bejne/fn-ptNaIhNnSiM4.html. I'm working on a follow up to both that one and the one from this comment. It'll be live in a few weeks.

We have a deployment mission problem…let's use k8s…great…now we have two problems😂