With the current pace of feature releases in OBI and with our emphasis on stable versioning, it makes it hard to let people test out features until we decide to cut an official release.
there is always an option to take the main image but its a mutable tag and can release between pull versions.
My suggestion is to have a similar workflow to the otel collector nightly release. running every night and releasing 2 docker images.
Versioned: ebpf-instrument:0.10.0-nightly.<shortcommit> - immutable
Ephemeral: ebpf-instrument:nightly - mutable
This can run for both obi and the k8s-cache components.
With the current pace of feature releases in OBI and with our emphasis on stable versioning, it makes it hard to let people test out features until we decide to cut an official release.
there is always an option to take the
mainimage but its a mutable tag and can release between pull versions.My suggestion is to have a similar workflow to the otel collector nightly release. running every night and releasing 2 docker images.
Versioned:
ebpf-instrument:0.10.0-nightly.<shortcommit>- immutableEphemeral:
ebpf-instrument:nightly- mutableThis can run for both
obiand thek8s-cachecomponents.