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

Submariner -- Skip Certificate Verification #1198

Closed
jgrap opened this issue Mar 29, 2021 · 1 comment
Closed

Submariner -- Skip Certificate Verification #1198

jgrap opened this issue Mar 29, 2021 · 1 comment
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@jgrap
Copy link

jgrap commented Mar 29, 2021

What happened:
On deployment of Submariner, it is observed that Lighthouse Agent is failing at certificate verification. The initial error looked like the following: x509: certificate is valid for 172.30.0.1, not 10.5.57.171
After attempting to add an additional certificate for the 10.5.57.171 to be served from the API server, I am still observing the following: x509: certificate signed by unknown authority

It does not appear that Submariner currently supports skipping this verification.

What you expected to happen:
The expectation is that Submariner allows the ability to skip certificate verification for testing purposes.

How to reproduce it (as minimally and precisely as possible):

  1. Deployment of on-prem OpenShift 4.6 utilizing self-signed certificates
  2. Deploy Submariner via Helm guide: https://submariner.io/operations/deployment/helm/
  3. Lighthouse Agent is in a crash loop, failing on start up with validating certificates

Environment:

  • Submariner version (use subctl version): 0.7.0
  • Kubernetes version (use kubectl version): 1.19.0
  • Cloud provider or hardware configuration: On-prem virtualized
  • Install tools: Helm
  • Other: OpenShift 4.6
@jgrap jgrap added the bug Something isn't working label Mar 29, 2021
@stale
Copy link

stale bot commented May 30, 2021

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label May 30, 2021
@stale stale bot closed this as completed Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant