After installing a new self-signed certificate into Velum, Kubernetes only sees "certificate has expired or is not yet valid" error
This document (7023112) is provided subject to the disclaimer at the end of this document.
Environment
SUSE CaaS Platform 3.0
Situation
After installing a new self-signed certificate into Velum, Kubernetes
only sees "certificate has expired or is not yet valid" error.
Resolution
When adding a certificate into Velum, the entire URL must be used including the port number, please see below:
Incorrect URL: smt.example.com
Correct URL: https://smt.example.com:5000
After applying the change, Velum will re-bootstrap. Any failed pods should be killed and they will automatically be recreated using the new certificate.
Cause
Incorrectly specifying the certificate URL (Uniform Resource Locator) during creation.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7023112
- Creation Date: 19-Jun-2018
- Modified Date:03-Mar-2020
-
- SUSE Caas Platform
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
