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

help needed : OpenStack cinder https certificate #78

Open
olivierBlanc opened this issue Feb 8, 2021 · 2 comments
Open

help needed : OpenStack cinder https certificate #78

olivierBlanc opened this issue Feb 8, 2021 · 2 comments

Comments

@olivierBlanc
Copy link

Hello,
When trying to connect cinder to OpenStack tenant, I have a self-signed certificate problem (x509: certificate signed by unknown authority)
Is there a way to give the cinder driver, through the configuration, a ca-file to bypass this problem ?
Regards,
Olivier

@sushanthakumar
Copy link
Contributor

@olivierBlanc , Can you elaborate a bit on your scenario. Are you using openstack which is integrated with soda projects?

@olivierBlanc
Copy link
Author

Hi,

Yes, I am using OpenStack integrated with Soda Project.

So my infrastructure is IaaS with Openstack. I installed a Kubernetes v1.20.2 on this infra and I want to be able to access OpenStack volumes from my Pods in RWM mode.
To do so, I moved to SODA.

For my problem, I tried to move on and I modified the cinder.go file in contrib/drivers/openstack to add a parameter CAPEM read from cinder.yaml configuration file.
I pass this info to gophercloud/gophercloud/openstack/client.go AthenticatedClient function. I modified that function too, to initiate an http client transport aware of the RootCA to use.

From now on I bypassed the self-certificate problem that I had.
I'm still going on to check other problems that I have with my configuration file.
Let me know if I need to provide more infos, code or whatever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants