-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 support for play/generate kube PersistentVolumeClaims and Podman volumes #9935
Add support for play/generate kube PersistentVolumeClaims and Podman volumes #9935
Conversation
@EduardoVega looks like you've some trailing space issues. |
6e14a90
to
854679d
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EduardoVega, rhatdan 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 |
pkg/domain/infra/abi/play.go
Outdated
// attributes, so they can be configured using annotations since they will not affect k8s. | ||
for k, v := range pvcYAML.GetAnnotations() { | ||
switch k { | ||
case "podman.volume/driver": |
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.
2 questions for consideration:
- should these be kept as constants anywhere?
- often, these special annotations follow the format of a url:
io.podman.volume
does it make sense to apply that here?
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.
- Let me change that.
- You're correct. The url format does not provide any special functionality but it is better to stick to the k8s syntax. What about something like this
volume.podman.io/driver
based onnode.kubernetes.io/instance-type
?
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 has been changed.
A couple of questions but none of them blocking. This looks great @EduardoVega, I especially like the idea about using annotations to get special podman options |
Signed-off-by: Eduardo Vega <[email protected]>
854679d
to
61cb6d6
Compare
/lgtm |
Thanks @EduardoVega |
Signed-off-by: Eduardo Vega [email protected]
This PR provides the ability to support Kubernetes PersistentVolumeClaims for podman play or generate kube. A k8s PersistentVolumeClaim represents a Podman volume, only the PVC name is required to create the volume. Podman volume options can be set using PVC annotations.
This is based on this PR #8266 and related to this Issue #5788.