Bug 1384140 - Deploying High Availability Router still uses --credentials
Summary: Deploying High Availability Router still uses --credentials
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 16:03 UTC by Eric Jones
Modified: 2019-12-16 07:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-26 13:25:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Jones 2016-10-12 16:03:57 UTC
Document URL: 
https://docs.openshift.com/container-platform/3.3/admin_guide/high_availability.html#configuring-a-highly-available-routing-service

Section Number and Name: 
Cluster Administration 
High Availability

Describe the issue: 
The command to deploy the highly available router still uses [0] which produces a flag message [1].

[0]    --credentials=/etc/origin/master/openshift-router.kubeconfig \
Suggestions for improvement: 

[1] Deprecation:
Flag --credentials has been deprecated, use --service-account to specify the service account the ipfailover pod will use to make API calls

Additional information: 
Stop using the --credentials option and either replace it exclusively with the --servce-account option (part of the command as well) or replace it with whatever option is necessary to deploy properly.

Comment 2 Michael Burke 2018-04-26 13:25:09 UTC
Closing fixed through other means. Per 3.3 rev history:
|xref:../admin_guide/router.adoc#admin-guide-router[Monitoring Routers]
|Removed references to the deprecated `--credentials` option.


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