Bug 1501994 - No documentation related to the configuration of serviceServingCert
No documentation related to the configuration of serviceServingCert
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
All Linux
unspecified Severity high
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2017-10-13 12:36 EDT by Matthew Robson
Modified: 2018-03-02 03:01 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Robson 2017-10-13 12:36:20 EDT
Document URL: 

[1] https://docs.openshift.com/container-platform/3.6/dev_guide/secrets.html#service-serving-certificate-secrets

[2] https://docs.openshift.com/container-platform/3.6/install_config/upgrading/manual_upgrades.html

Section Number and Name: 

[1] Service Serving Certificate Secrets

[2] Upgrading Master Components OR Upgrading Cluster Metrics OR Additional Manual Steps Per Release

This was introduced in OCP 3.3, but without this config, you can not upgrade to metrics in OCP 3.6 as it leverages this component. It's mandatory as of 3.6.

Describe the issue: 

No details on how to configure serviceServingCert and create the certificates in the master-config.yaml 

      certFile: service-signer.crt
      keyFile: service-signer.key

Suggestions for improvement: 

Add details on serviceServingCert in master-config and how to generate the certs:

oc adm ca create-signer-cert --cert=service-signer.crt --key=service-signer.key --name=openshift-service-serving-signer --serial=service-signer.serial.txt

Additional information:

This is done in ansible:

But if someone does a manual upgrade, this is not done.

Note You need to log in before you can comment on or make changes to this bug.