vdemeester

tekton-oracle cluster — work streams analysis (2026-05-13)

Status: node 10.0.128.239 recovered ✅

Rebooted via OCI CLI, now Ready again. Still need Fluent Bit memory fix (100M → 256M).

---

1. PVC sprawl — 220 PVCs, only 5 in use

The numbers

vdemeester

Tekton Plumbing Roadmap

How Tekton builds, tests, and releases itself — and where we're heading.

This roadmap covers the infrastructure, CI/CD, and tooling that supports the tektoncd project. It is organized by workstream and prioritized using NOW / NEXT / SOON / LATER buckets.

Bucket	Meaning

vdemeester

@/tmp/test-alignment-report-v2.md

vdemeester

Diátaxis audit of Tekton Pipelines documentation

Diátaxis Audit of Tekton Pipelines Documentation

Audit of all 64 markdown files in docs/ against the Diátaxis documentation framework. Each document is classified by its primary type and whether it mixes types (hybrid).

Classification Key

| Type | Orientation | User need | Icon |

vdemeester

Tekton Maintainer Triage Report

Date: March 6, 2026 Period analyzed: March 2025 – March 2026 (last 12 months) Data sources: GitHub API (PRs authored, PR reviews, issue comments, commits), Tekton DevStats (contributions, reviews, PRs, comments, commits), OWNERS files, org.yaml

Methodology

Per the Tekton Contributor Ladder:

• Inactivity threshold: >4 months of no contributions, or >2 months of no communication

vdemeester

#!/bin/bash

set --noprofile --norc -e -o pipefail

# Test script to validate the detect logic from ci.yaml

echo "Testing detect logic for non-docs and yaml outputs"
echo "==================================================="
echo ""

vdemeester

How did you get involved with Open Source?

I've always wanted to do Open Source, since I discovered it around 1999. The first Linux distribution I used was Red Hat Linux, and that was also my first encounter with Linux and Open Source. Little did I know that 20 years later I would work for the company that kind of introduced me to it!

I initially started looking into small projects I would need in my first startup job, like fog/fog, but what really got me started was the Docker project. Docker organized those "contribute meetups" in different places around their "birthday" and so, I made my first pull-request to the project that way. And from that point on, I was hooked. I also got involved a bit in the Archlinux User Repository when I was using it and now in NixOS.

What’s Open Source to you?

For me, Open Source is "the way" to do things. I truly believe into sharing commons and the fact that we do better when we work together, in the open. And Open Source embodies that.

vdemeester

package main

import (
	"context"
	"fmt"
	"log"
	"os"
	"path/filepath"
	"strings"

vdemeester

{"severity":"info","timestamp":"2023-03-28T13:12:45.869Z","logger":"tekton-pipelines-webhook","caller":"webhook/conversion.go:45","message":"Webhook ServeHTTP request=&http.Request{Method:\"POST\", URL:(*url.URL)(0xc0003fdb00), Proto:\"HTTP/1.1\", ProtoMajor:1, ProtoMinor:1, Header:http.Header{\"Accept\":[]string{\"application/json, */*\"}, \"Accept-Encoding\":[]string{\"gzip\"}, \"Content-Length\":[]string{\"24910\"}, \"Content-Type\":[]string{\"application/json\"}, \"User-Agent\":[]string{\"kube-apiserver-admission\"}}, Body:(*http.body)(0xc0006b9ec0), GetBody:(func() (io.ReadCloser, error))(nil), ContentLength:24910, TransferEncoding:[]string(nil), Close:false, Host:\"tekton-pipelines-webhook.tekton-pipelines.svc:443\", Form:url.Values(nil), PostForm:url.Values(nil), MultipartForm:(*multipart.Form)(nil), Trailer:http.Header(nil), RemoteAddr:\"10.244.0.1:9861\", RequestURI:\"/resource-conversion?timeout=30s\", TLS:(*tls.ConnectionState)(0xc000e14420), Cancel:(<-chan struct {})(nil), Response:(*http.Response

vdemeester

Local execution of Pipelines

Agenda

An exploration of how and why running our pipelines locally.

• Why ?