diff options
| author |   Huabing Zhao <zhao.huabing@zte.com.cn> | 2020-04-26 09:09:38 +0800 |
|---|---|---|
| committer |   Sylvain Desbureaux <sylvain.desbureaux@orange.com> | 2020-05-04 13:28:34 +0000 |
| commit | bb524567ce79ec88c4b586bc842056ac4f90ca1f (patch) | |
| tree | 42faca808caae7e160d1b80df44b97ed5dacd649 /docs/oom_hardcoded_certificates.rst | |
| parent | 006318ac37142eb823db4a2074ce6c8ad1629166 (diff) | |
Release RC1
This change addresses two issues:
MSB-467: Certificate in MSB is set to use *.zte.com.cn
MSB-462: Pods still run as root
These two issue have been fixed in docker images, but also need to be
reflected in K8s manifest.
Issue-ID: MSB-467
Signed-off-by: Huabing Zhao <zhao.huabing@zte.com.cn>
Change-Id: Id67e521b3051e9651051083f05d9e54973803030
Diffstat (limited to 'docs/oom_hardcoded_certificates.rst')
| -rw-r--r-- | docs/oom_hardcoded_certificates.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/oom_hardcoded_certificates.rst b/docs/oom_hardcoded_certificates.rst index 7706f2cd2d..244fab4d50 100644 --- a/docs/oom_hardcoded_certificates.rst +++ b/docs/oom_hardcoded_certificates.rst @@ -30,6 +30,8 @@ Here's the list of these certificates: +------------------+------------------+------------------+--------------------------------------------------------------------------------------------+ | APPC | Yes | No | No | kubernetes/appc/resources/config/certs/org.onap.appc.p12 | +------------------+------------------+------------------+--------------------------------------------------------------------------------------------+ + | MSB | Yes | No? | Yes | kubernetes/msb/resources/config/certificates | + +------------------+------------------+------------------+--------------------------------------------------------------------------------------------+ | SDC | Yes | No? | No? | kubernetes/sdc/resources/cert | +------------------+------------------+------------------+--------------------------------------------------------------------------------------------+ | SO | Yes | No? | Yes | kubernetes/so/resources/config/certificates | |