-
Notifications
You must be signed in to change notification settings - Fork 523
Release MongoDB Kubernetes Operator v0.11.0 #1601
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
Conversation
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.
Congratulations for your first release !
Left a few comments regarding spelling and syntax on the release notes
Otherwise LGTM, well done
docs/RELEASE_NOTES.md
Outdated
|
||
All container images published for the community operator are signed with our private key. This is visible on our Quay registry. Signature can be verified using our public key, which is available at [this address](https://cosign.mongodb.com/mongodb-enterprise-kubernetes-operator.pem). | ||
## Documentation improvements | ||
Improvements were made to the documentatio of using the community operator as well as the one for local development. |
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.
Small typo here
docs/RELEASE_NOTES.md
Outdated
## ReadinessProbe error logging | ||
- fixed a red herring which caused the probe to panic when the health status is not available. Instead it will just log the error | ||
## Bug Fixes | ||
- Users removed from the resource are now also deleted from the database and their connection string secretes are cleaned up |
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.
Typo here as well (secretes)
docs/RELEASE_NOTES.md
Outdated
- fixed a red herring which caused the probe to panic when the health status is not available. Instead it will just log the error | ||
## Bug Fixes | ||
- Users removed from the resource are now also deleted from the database and their connection string secretes are cleaned up | ||
- Colisions of the scram secret name will now be spotted by spec validation |
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.
Typo as well here (spelling)
I would rephrase it with something like "Scram secret name collisions will now be caught when validating specs."
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.
LGTM!
Review and publish the release here: https://github.com/mongodb/mongodb-kubernetes-operator/releases |
Summary:
helm changes: mongodb/helm-charts#340
All Submissions:
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).