hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9K
active users

#Skaffold

0 posts0 participants0 posts today
Replied to viq

@viq Hey, viq, using #skaffold and #helm for deploying Kubernetes is a less flexible approach to deploying manifests. Eventually, you will face the rigidity of this technique. I would consider rewriting the deployment pipeline. What you need is yaml files at the end of the day, anyway. A simple #kubectl can deal with that. You can get the yamls from the `helm template` command and post-process them with, e.g., #kustomize—a simple and battle-tested solution.
[1/2]

Continued thread

- lifecycle hooks of #skaffold. But we don't build any image, sync doesn't seem to do anything, and pre-deploy is too late to be able to see what would get done
- just commit those files to repo, and have a script to update them

Is there some other option I didn't think of?
[2/2]

#kubernetes question: our deployment stack is #skaffold plus #helm. We have #OpenEBS deployed, I'm trying to add their monitoring mixin to deployment. But they want to deploy whole kube-prometheus, which we already have. I have a script to generate their manifests and grab just those 4 files we're interested in, and have helm grab those. But here comes the question: how do I tie in the generation with the rest of the deployment?
[1/2]