Bug 1323670 - [DOCS] Allow correct service Account
Summary: [DOCS] Allow correct service Account
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Thien-Thi Nguyen
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 12:10 UTC by Jaspreet Kaur
Modified: 2019-10-10 11:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 16:21:41 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jaspreet Kaur 2016-04-04 12:10:56 UTC
Document URL: https://access.redhat.com/documentation/en/openshift-enterprise/3.1/installation-and-configuration/chapter-18-aggregating-container-logs

Section Number and Name: 3.Create the deployer service account

 oc policy add-role-to-user edit \
            system:serviceaccount:default:logging-deployer

Describe the issue: The command is incorrect. It should be 

 oc policy add-role-to-user edit \
            system:serviceaccount:logging:logging-deployer

Suggestions for improvement: Also, the guide is unclear on purpose kibana-ops and how it can be enabled. Where we can see operations log and where we can see project logs. Which user can see which logs and how can we access and work with kibana ui.


Sizing of dedicated nodes havent been mentioned. If the nodes doesn't have enough RAM say 8G the logging-deployer will never start leading to an error without any indication. So atleast the prerequisite should be mentioned for deploying efk stack or else advice to reduce ES_INSTANCE_RAM which is 8G default.

Additional information:

Comment 3 Thien-Thi Nguyen 2016-06-23 16:21:41 UTC
This error was corrected in:
https://github.com/openshift/openshift-docs/commit/35a37534905bb5b60a1e9d90fe63800d8fe70b43
(which does not seem to be connected with any PR or BZ as far as i can tell).  The change removed ":default:" but did not replace it w/ ":logging:".  Rather, it made use of the ‘--serviceaccount’ option that achieves the same end:

$ oc policy add-role-to-user edit --serviceaccount logging-deployer

Moving to CLOSED CURRENTRELEASE.

Vikram: Any idea on how to map that commit to some tracking PR or BZ?

Comment 4 Vikram Goyal 2016-07-18 01:19:27 UTC
(In reply to Thien-Thi Nguyen from comment #3)
> This error was corrected in:
> https://github.com/openshift/openshift-docs/commit/
> 35a37534905bb5b60a1e9d90fe63800d8fe70b43
> (which does not seem to be connected with any PR or BZ as far as i can
> tell).  The change removed ":default:" but did not replace it w/
> ":logging:".  Rather, it made use of the ‘--serviceaccount’ option that
> achieves the same end:
> 
> $ oc policy add-role-to-user edit --serviceaccount logging-deployer
> 
> Moving to CLOSED CURRENTRELEASE.
> 
> Vikram: Any idea on how to map that commit to some tracking PR or BZ?

Sorry Thien-Thi. I missed this notification.

If it was already fixed due to another PR, no need for tracking.


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