-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Refactor GlusterFS PV spec. #60195
Refactor GlusterFS PV spec. #60195
Conversation
@humblec: Adding do-not-merge/release-note-label-needed because the release note process has not been followed. One of the following labels is required "release-note", "release-note-action-required", or "release-note-none". 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. |
7131438
to
294cff7
Compare
89f674b
to
37d535f
Compare
04ba51f
to
c7229d5
Compare
72c1962
to
bef2bd7
Compare
bef2bd7
to
b015786
Compare
/retest |
@LiGgit hopefully last commit has addressed return from |
/retest |
API lgtm, go ahead and squash in the review commits needs ack from @kubernetes/sig-storage-pr-reviews on the GetVolumeName() change |
linting error as well:
|
@@ -191,7 +191,7 @@ type PersistentVolumeSource struct { | |||
// exposed to the pod. Provisioned by an admin. | |||
// More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md | |||
// +optional | |||
Glusterfs *GlusterfsVolumeSource `json:"glusterfs,omitempty" protobuf:"bytes,4,opt,name=glusterfs"` | |||
Glusterfs *GlusterfsPersistentVolumeSource `json:"glusterfs,omitempty" protobuf:"bytes,4,opt,name=glusterfs"` |
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.
Sorry I'm late to the party. Is this a backwards compatible change? Will clients that programatically interact with the API start failing because the type has changed?
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.
It is backwards compatible in the dimensions we guarantee.
The type of the go field does not impact what gets serialized to the wire, so the type change does not affect wire compatibility (against the API or against etcd).
The type of the go struct field is changing. Depending on how a client made use of this object, it might have to adjust how it constructed a struct of this type. If all it did was retrieve objects from the API and access fields (e.g. pv.Spec.Glusterfs.EndpointsName
) no change would be required. Go struct compatibility is not currently guaranteed release-to-release.
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.
Ah ok, so if someone synced their go-client to the latest, then it's possible they will have to recompile, but older applications using the old clients will continue to work. Is this something we need to call out in any release notes?
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, worth a release note, both for the new capability, and for the client-go impact
97de0a9
to
6d41f24
Compare
This patch introduces glusterfsPersistentVolumeSource addition to glusterfsVolumeSource. All fields remains same as glusterfsVolumeSource with an addition of a new field called `EndpointsNamespace` to define namespace of endpoint in the spec. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
6d41f24
to
bdb051c
Compare
Thanks a lot @liggitt ! The commits are squashed and test are green :).. |
/retest |
/lgtm /hold |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: humblec, liggitt, msau42 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 |
/hold cancel |
Before it only checked spec.ReadOnly, but now it checks spec.pv.spec.glusterfs.readonly flag. This patch also correct a bug in old code where it returned mounter true even when pv is false. This is a follow up PR based on comment# kubernetes#60195 (comment) Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
…ble to gluster: AD controller kubelet volume manager actual/desired sw for attachable volumes volume reconstruction This is a followup PR based on comment# kubernetes#60195 (comment) Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
Signed-off-by: Humble Chirammal hchiramm@redhat.com
Special notes for your reviewer:
Release note: