-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add Changelog for 1.1.0 #45
Conversation
/hold |
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.
Do we need to release a new version? Or should we just deprecate and stop releasing the entire sidecar?
* release tools: fix "canary" + enhance testing ([#23](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/23)) | ||
* Update usage and deployment documentation ([#20](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/20)) | ||
* Add more details about cluster-driver-registrar ([#10](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/10)) | ||
* Auto-detect AttachRequired ([#4](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/4)) |
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.
This change removed a command line flag, which is breaking. It's also alpha so I think that's fine, but we should call it out
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.
Fixed + added note about -pod-info-mount-version
-> -pod-info-mount
.
We should have a bot that compares --help
output :-)
|
||
## Other notable changes | ||
|
||
* Use distroless as base image ([#39](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/39)) |
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.
Nice job on all the comments. Did you do this by hand?
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.
I get PR numbers from all merge commits since the last release + get titles of these PRs. + some manual editing.
Stay tuned for kubernetes-csi/docs#142!
/approve |
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
/LGTM |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: childsb, jsafrane, vladimirvivien The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@msau42, PTAL
Note: not bumped to 2.0, IMO "action needed" is enough