-
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
kube: configmap
volume should be reused if already exists
#13732
kube: configmap
volume should be reused if already exists
#13732
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc 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 |
`podman play kube` creates a new volume for configmap, if same configmap is applied again volume can be re-used, there is no need to remove and re-create the volume again Signed-off-by: Aditya R <[email protected]>
e3464c4
to
daeea48
Compare
LGTM |
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
But I think the logic would be cleaner if you invert the logic:
not error.Is() -> return
This way you could drop the else block due the early return.
/lgtm |
@Luap99 Yes we can do get first and create new volume later, I'll open a follow-up. |
No that is not what I am saying. I just want that the newly added if else logic is inverted. This way you can drop the else because you would return in the if block. |
podman play kube
creates a new volume for configmap, if same configmapis applied again volume can be re-used, there is no need to remove and
re-create the volume again
Closes: #13715