cloud-provider-openstack
cloud-provider-openstack copied to clipboard
kubernetes
[Barbican][KMS] Fix clouds.yaml authentication
What this PR does / why we need it: With the barbican KMS plugin it's impossible to use clouds.yaml authentication.
Which issue this PR fixes(if applicable): fixes #2895
Special notes for reviewers:
Release note:
[barbican-kms-plugin] Enable the use of clouds.yaml based authentication
Welcome @modzilla99!
It looks like this is your first PR to kubernetes/cloud-provider-openstack 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes/cloud-provider-openstack has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @modzilla99. Thanks for your PR.
I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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-sigs/prow repository.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kayrus
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [kayrus]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/cherry-pick release-1.33 /cherry-pick release-1.32 /cherry-pick release-1.31
@kayrus: once the present PR merges, I will cherry-pick it on top of release-1.31, release-1.32, release-1.33 in new PRs and assign them to you.
In response to this:
/cherry-pick release-1.33 /cherry-pick release-1.32 /cherry-pick release-1.31
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-sigs/prow repository.
@kayrus: new pull request created: #2926
In response to this:
/cherry-pick release-1.33 /cherry-pick release-1.32 /cherry-pick release-1.31
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-sigs/prow repository.
@kayrus: new pull request created: #2927
In response to this:
/cherry-pick release-1.33 /cherry-pick release-1.32 /cherry-pick release-1.31
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-sigs/prow repository.
@kayrus: new pull request created: #2928
In response to this:
/cherry-pick release-1.33 /cherry-pick release-1.32 /cherry-pick release-1.31
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-sigs/prow repository.