Release v7.0.0

[pjuarezd]

This release will require also a sidecar release with image name quay.io/minio/operator-sidecar:v7.0.0

[ravindk89]

What is the migration/upgrade path here?

What needs to change on an existing tenant for the update to work?

Or are these not expected to break workflows if you have a tenant using them?

[pjuarezd]

For the Tenant CRD is as simple as update the Operator version, it is not going to be disruptive at all.
For the MinIO Job there is no replacement in the Operator, AIStor have a similar functionality for enterprise, the AdminJob, I would say the recommendation if MinIOJob is needed, to move to the AIStor operator

[ravindk89]

So if someone has an existing MinioJob YAML its just going to stop working with 7.0.

FOr PDB same - do they have to scrub PDB from tenant first?

[pjuarezd]

right, MinIOJob will stop working on 7.0.0

[ramondeklein]

MinIOJob is a one-time operation.

@pjuarezd Does Helm remove the CRD during upgrade? If not then we may want to add code to deal with this.

[pjuarezd]

yes, the Helm upgrade will remove the CRD @ramondeklein

[donatello]

1. Is the sidecar here a new component?
2. What is the release steps to build and publish it?
3. Is minio/operator to be released with goreleaser in the usual way?

[pjuarezd]

1. Is the sidecar here a new component?
2. What is the release steps to build and publish it?
3. Is minio/operator to be released with goreleaser in the usual way?

I think we can do the release the old way, using goreleaser, sidecar/ subdir has a .goreleaser file as well.

operator sidecar is already on quay https://quay.io/repository/minio/operator-sidecar?tab=tags