
Misverstand: Jezus de timmerman
Schrijnwerker, niet per se Jezus (Musée Saint-Rémi, Reims)Het is een standaardscène in vrijwel elke film over Jezus: de flashback waarin iemand terugdenkt aan hoe het allemaal begon, met een jonge Jezus die in Nazareth nog tafels en andere meubels timmerde. In Jesus Christ Superstar (1973) herinnert Judas eraan dat “tables, chairs, and wooden chests would have suited Jesus best” en in The Passion of the Christ (2004) is de timmermanszoon uit Nazaret zelfs de uitvinder van een nieuw soort meubilair.
Het maken van meubels was echter het werk van een schrijnwerker, terwijl Jezus (volgens Marcus 6.3 || Matteüs 13.55) van beroep timmerman was – of beter, een bouwkundig vakman, wat vermoedelijk de beste vertaling is van het Griekse tektôn.
#historischeJezus #JesusChristSuperstar #JezusVanNazaret #NieuweTestament #tektôn #ThePassionOfTheChrist #timmerman
In my rush to get a basic docker build tekton pipeline working I made a bit of a noob mistake... Using an emptyDir workspace to store data between tasks.
I didn't realise that the emptyDir workspace is only persisted for the duration of a specific task so at the end of the clone task it's discarded and a fresh emptyDir is supplied for the build task...
I was caught off guard cos I didn't really think that would be too useful but after doing some reading it's probably used when running/testing single tasks in isolation. Using it for CI/CD would mean you're not getting the benefit of cached data between runs.
Setting up a PVC won't take long, I'm just being lazy. Serves me right.
Spent a little time this weekend getting to know Tekton
People use it at work to build a golden path CI/CD pipeline in the form of a helm chart and it'd be nice if I could dive in and make changes to push upstream as needed.
So far, all I've really done is gone over some of the examples:
https://tekton.dev/docs/getting-started/
Pretty happy with it so far, set up is much easier than gitea actions and I think this will just be easier to maintain. The kubernetes/manifest-driven interface fits nicely with my gitops/fluxcd strategy but I can still trigger builds manually with the CLI as needed.
Next step is to port over some of my existing image builds and then I'll see if I can make my own image build pipeline as a helm chart so it's reusable.
Anyone have any interesting use cases for Tekton in their own work/home?
#tekton #cicd #gitops #fluxcd #docker #helm #homelab #selfhosted
Tekton released version 1.0
https://tekton.dev/blog/2025/05/23/tekton-pipelines-reaches-1.0-stability-today-innovation-tomorrow/
Finally merged my #Tekton experiment.
Added 34000 lines of YAML to drop 62. Not the best ratio 😅
But let's see where things go from here. I'm quite confident that I'll be able to replace gitlab-runners in the next few weeks and find a good pattern for the pipelines.
But I think I'll take a day off working on these. It's so crazy abstract, but that's also the potential tekton holds.
This patch introduces Tekton pipelines and Tekton triggers to the cluster. This should provide a new, independent way to run pipelines across various git forges. It's a preparation of changing...
Anyone interested in talking about Tekton? I would like to have a chat about it.
I'm currently migrating my CI workflow to it and I'm wondering what other people's experience is.