So this is probably the wrong place, but I'm not sure to where's a better place to ask. Is there an example combining both tekton pipelines and fluxcd for gitops?
Flux is most useful when used as a deployment tool at the end of a Continuous Delivery pipeline (like Tekton!!!) . Flux will make sure that your new container images and config changes are propagated to the cluster.
Flux is really three things, which are munged together for those historical reasons we're always hearing about.
I would ideally like to have a github pull request trigger a tekton pipeline which will build an image, and push it to a docker registry, and then have flux update my manifest image refs in git, and apply them to a kubernetes cluster. However, I could avoid polling a docker registry if a tekton pipeline were to use the flux api or command line tooling to update the manifest image refs..
Is that something that someone has already got working?
This was the first I'd heard of Flux, so thanks for the heads-up. I'm not aware of anyone already getting these two tools running together but I don't see anything immediately problematic in the description of how Flux operates.
Running specific containers and command line tools as part of a Tekton Task is eminently doable - in fact it's how they fundamentally work. See the steps field in the Task spec here: https://github.com/tektoncd/pipeline/blob/master/docs/tasks.md#syntax
Calling an API is likewise easy to do given the right Secrets and container / CLI tools to make the requests.
I'm going to close this issue since it's not really an issue with Tekton Pipelines per se and instead suggest that you join us on Slack to try and find people interested in a similar use case to your own: https://github.com/tektoncd/community/blob/master/contact.md#slack
Chatted with @bobcatfish about this a bit more who thought this would be an excellent opportunity to develop a Catalog entry that shows how to tie the two systems together. I'm going to reopen this issue for anyone who is interested in working on this further!
Hi @sbwsg ,
I'm new to tekton, I think this issue is a good opportunity to start contributing,
Can I work on it?
Thanks :)
sure thing, have at it @medkbadri !
@medkbadri are you still working on (or planning to work on) this issue?
@dibyom
Hey, I will update asap (already working with tetkton and flux combined in a project for my company)
will just clean files
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@medkbadri I don't suppose you have the unclean files lying around anywhere, do you?
Also interested on this. How is the progress going? Can I help? @medkbadri
Tekton can build and publish images, Flux should be able to detect the new images and update the cluster accordingly.
They should operate quite separately, is there something needed at all ?
Most helpful comment
@dibyom
Hey, I will update asap (already working with tetkton and flux combined in a project for my company)
will just clean files