On Sat, Mar 8, 2025, at 2:50 AM, Richard W.M. Jones wrote:

> I didn't watch his talk, but this all sounds very vague.  And that the
> fact that it's "container first" and an internal project first is
> worrying too. 

One very important thing to understand here is that Konflux is built on *top* 
of https://tekton.dev/ which itself is built on top of Kubernetes 
https://kubernetes.io/ which are well documented and established FOSS projects 
used by multiple organizations, with a wealth of knowledge and tooling built on 
top of both of them. Which is not true of Koji.

Just one example: In the past we've hit issues where some RPMs take a lot more 
CPU/RAM to build than others.

In Kubernetes, projects like 
https://github.com/kubernetes/autoscaler/tree/9f87b78df0f1d6e142234bb32e8acbd71295585a/vertical-pod-autoscaler
 exist to automatically track and scale the requested resources for pods 
(containers) based on historical or inferred usage. Because Tekton builds 
(tasks) are just pods ( https://tekton.dev/docs/pipelines/podtemplates/ ) these 
techniques work for them.

But for Koji, there's no such ecosystem, and only ad-hoc bespoke ways to tell 
the system how much resources a particular build requires.

Strongly related to this is that Koji is a bespoke task manager mostly used to 
build RPMs, but has little to do with running generic workloads (especially 
relevant: integration tests running in containers) so we end up with disjoint 
infrastructure. With Tekton it's way more obvious how to e.g. build a container 
(or an RPM which is installed into a built container) and then run tests on 
that container before e.g. promoting it on, within the same cluster or CI job.

-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to