Bug 1290491 - [DOCS] Upgrading Manually
Summary: [DOCS] Upgrading Manually
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-10 16:34 UTC by Ryan Howe
Modified: 2017-12-30 06:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-30 06:12:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Howe 2015-12-10 16:34:22 UTC
Document URL: https://docs.openshift.com/enterprise/3.1/install_config/upgrades.html#upgrading-masters

Section Number and Name: Create the following master proxy client certificates:

Describe the issue: 

With 3.1 the master need the following hostname added to the certs. 

All certs in the master would need the following hostnames:

kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, master.example.com, Dopenshift, openshift.default, openshift.default.svc, openshift.default.svc.cluster.local, 10.3.8.242, 172.17.28.5, 172.30.0.1, IP Address:10.3.8.242, IP Address:172.17.28.5, IP Address:172.30.0.1


Suggestions for improvement: 

Would need to recreate the following certs and keys:
 
etcd.server.crt
etcd.server.key
 
master.proxy-client.crt 
master.proxy-client.key

master.server.crt
master.server.key

Comment 1 Scott Dodson 2015-12-14 03:20:55 UTC
Why do the etcd server certs need to be regenerated?


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