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.

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

Merged

Conversation

flouthoc
Copy link
Collaborator

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

Closes: #13715

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 31, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2022
`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]>
@flouthoc flouthoc force-pushed the reuse-configmap-volume branch from e3464c4 to daeea48 Compare March 31, 2022 09:37
@rhatdan
Copy link
Member

rhatdan commented Mar 31, 2022

LGTM

@flouthoc flouthoc requested a review from Luap99 March 31, 2022 11:26
Copy link
Member

@Luap99 Luap99 left a 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.

@Luap99
Copy link
Member

Luap99 commented Mar 31, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2022
@openshift-merge-robot openshift-merge-robot merged commit 4ba71f9 into containers:main Mar 31, 2022
@flouthoc
Copy link
Collaborator Author

@Luap99 Yes we can do get first and create new volume later, I'll open a follow-up.

@Luap99
Copy link
Member

Luap99 commented Mar 31, 2022

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.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue with volumes when recreating a pod
4 participants