-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v7.0.0 #2367
Open
pjuarezd
wants to merge
5
commits into
minio:master
Choose a base branch
from
pjuarezd:release-7
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Release v7.0.0 #2367
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# MinIO Operator v7.0.0 release notes | ||
|
||
## About this release | ||
|
||
MinIO Operator is the recommended production-ready way to manage MinIO deployments in Kubernetes. This version includes a new base version requirements, deprecations, bugfixes and more. | ||
|
||
## What’s new? | ||
|
||
Operator 7.0.0 is now available. This release requires Kubernetes version 1.29.0 or later. | ||
If your cluster does not use Kubernetes version 1.29.0 or later, you must upgrade your cluster to before installing or upgrading to Operator v7.0.0+. | ||
|
||
Some breaking changes motivates a major release, here is the list of breaking changes: | ||
|
||
* remove minioJob | ||
* remove Pod Distribution Budget (PDB) | ||
|
||
Additionally several bugfixes are included in this version: | ||
|
||
* Add storageLabels value to tenant chart in https://github.com/minio/operator/pull/2335 | ||
* Allow custom (non-propagating) stateful set metadata in https://github.com/minio/operator/pull/2337 | ||
* feat:add portName to container in https://github.com/minio/operator/pull/2347 | ||
* fix: incorrect error log `Waiting for MinIO to be ready: %!s(<nil>)` in https://github.com/minio/operator/pull/2345 | ||
* Fix base example url in https://github.com/minio/operator/pull/2349 | ||
* Fix storageClassName references in tenant.pool.volumeClaimtemplates in https://github.com/minio/operator/pull/2362 | ||
* Add initContainers to tenant Helm Chart in https://github.com/minio/operator/pull/2366 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, MinIOJob will stop working on 7.0.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, the Helm upgrade will remove the CRD @ramondeklein
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So no other changes are required for upgrade? An existing tenant w/ PDB settings should still work in 7.0.0 - or are we asking them to scrub PDB settings first @pjuarezd