Support for cloud-provider-kind using podman rootless - #36
Open
bedge wants to merge 1 commit into
Open
Conversation
Add rootless Podman workflow for cloud-provider-kind One needs to avoid using sudo to run cloud-provider-kind when using podman on linux.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add rootless Podman workflow for cloud-provider-kind
One needs to avoid using sudo to run cloud-provider-kind when using podman on linux.
Result after starting cloud-provider-kind with this change:
Yes, I suppose one could do something fancy and automate the test for whether rootless podman was being used, but that's beyond my time availability.