Skip to content
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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Add Changelog for 1.1.0 #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions CHANGELOG-1.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
# Changelog since v1.0.1

## Actions needed

* Cluster admins must update RBAC rules. Previously, the cluster driver registrar created CSIDriver in `csi.storage.k8s.io/v1alpha1` API group, now it creates it in `csi.k8s.io/v1beta1`. See [deploy/kubernetes/rbac.yaml](deploy/kubernetes/rbac.yaml) for example.

* Command line flag `-driver-requires-attachment` has been removed. It is autodetected from the CSI driver.

* Command line flag `-pod-info-mount-version <string>` has been reworked into `-pod-info-mount <bool>`.

Please update your cluster-driver-registrar deployment files with these changes.

## Deprecations

* Command line flag `-connection-timeout` is deprecated and has no effect.


## Notable Features

* The cluster driver registrar now tries to connect to CSI driver indefinitely. ([#32](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/32))

* `CSIDriver` object is now beta and has been moved from `csi.storage.k8s.io/v1alpha1` to `csi.k8s.io/v1beta1`. New RBAC rules are required!

## Other notable changes

* Use distroless as base image ([#39](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/39))
Copy link
Member

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?

Copy link
Contributor Author

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!

* Use GetDriverName from csi-lib-utils ([#35](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/35))
* Minor RBAC update ([#34](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/34))
* Update compatibility matrix to only reflect branch head ([#27](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/27))
* Minor README updates ([#25](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/25))
* Migrate to k8s.io/klog from glog. ([#24](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/24))
* 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))
Copy link
Collaborator

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

Copy link
Contributor Author

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 :-)

* Use protosanitizer when logging ([#5](https://github.com/kubernetes-csi/cluster-driver-registrar/pull/5))