Konflux may integrate with KubeArchive in the future. To ensure that this integration is smooth, Konflux should install knative-eventing when it deploys to a cluster.
Unlike Tekton Results, which uses watchers to track when resuorces on the cluster change state, KubeArchive uses pub sub to get notified when resources on the cluster change state. KubeArchive uses ApiServerSource from knative-eventing to create cloudevents when kubernetes objects change state on the cluster. These cloudevents contain the definition of the Kubernetes object that they refer to. KubeArchive subscribes to these cloudevents and writes the Kuberenetes object definition contained in the cloudevent to a PostgreSQL database.
Konflux may integrate with KubeArchive in the future. To ensure that this integration is smooth, Konflux should install knative-eventing when it deploys to a cluster.
Unlike Tekton Results, which uses
watchers
to track when resuorces on the cluster change state, KubeArchive uses pub sub to get notified when resources on the cluster change state. KubeArchive usesApiServerSource
from knative-eventing to create cloudevents when kubernetes objects change state on the cluster. These cloudevents contain the definition of the Kubernetes object that they refer to. KubeArchive subscribes to these cloudevents and writes the Kuberenetes object definition contained in the cloudevent to a PostgreSQL database.