x509 front-proxy-ca cert/key should be the same on both controllers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Bart Wensley |
Bug Description
Brief Description
-----------------
While testing a related issue, I noticed that the front-proxy-
Severity
--------
Major (I believe this could cause addon API servers to fail over a swact due to key mismatch.)
Steps to Reproduce
------------------
Install StarlingX. Check the values of /etc/kubernetes
Expected Behavior
------------------
The certificate and key should match on both controller nodes.
Actual Behavior
----------------
The certificate and key do not match.
Reproducibility
---------------
Reproducible
System Configuration
-------
Two or more nodes.
Branch/Pull Time/Commit
-------
Day one issue, I think.
Last Pass
---------
Never
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Investigating failure of kubernetes conformance testing
Changed in starlingx: | |
assignee: | nobody → Bart Wensley (bartwensley) |
tags: | added: stx.containers |
Changed in starlingx: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: stx.3.0 stx.config |
Fix proposed to branch: master /review. opendev. org/698349
Review: https:/