Releases are broken

[chrisseto]

The release pipe line is currently gummed up. We have a buildkite job that watches for new tags getting pushed. When it sees them, it will run tests and then mint a release.

Notably, it seems that only v1 tests are run for the release. That in and of itself is a bit concerning to me.

@RafalKorepta recently tagged version v2.1.18 for release:

commit 3e1e2ddfdada263847790751a68f2a9f2ca06db6 (tag: v2.1.18-23.3.13)

Failures of kuttl/harness/decommission-on-delete are preventing anything from going out.

JIRA Link: K8S-218

[RafalKorepta]

The failure is comming from operator v1 end to end tests. The release is not blocked as tag does not perform full suite at this moment.

[chrisseto]

Does it not? From what I can cutting a tag triggers the k8s buildkite workflow which then runs task ci:k8s which runs goreleaser for the final task.

[chrisseto]

This tag v2.1.16-23.3.11 technically hasn't been released. I'm under the impression that goreleaser is what turns it into an actual "release".

[RafalKorepta]

It's complicated as migration tool, that is already removed, was creating artefacts to the release when tag was pushed to the repo. The release was published: https://github.com/redpanda-data/redpanda-operator/releases/tag/v2.1.16-23.3.11

For 2.1.18 and 2.1.17 we didn't have Github action run, so it didn't interrupted operator release process.