starlingx/docs
Code Issues Proposed changes

Update for collect tool enhancement to support any LDAP or WAD user account

Browse Source 
Change-Id: I94709d5b1db72121c27dcc60725dbf58de21b490
Signed-off-by: Suzana Fernandes <Suzana.Fernandes@windriver.com>
This commit is contained in:
Suzana Fernandes 2024-11-13 18:36:57 +00:00 committed by Juanita-Balaraj
parent df5f959cf3
commit 854eb3de54
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/fault-mgmt/kubernetes/troubleshooting-log-collection.rst
View File

@ -20,9 +20,14 @@ Collect Tool Caveats and Usage
.. _troubleshooting-log-collection-ul-dpj-bxp-jdb:
- Log in as **sysadmin**, NOT as root, on the active controller and use the
- Log in via SSH or local console on the active controller and use the
:command:`collect` command.
.. note::
The user must have sudo capability and be in the ``sys_protected`` group
to use the ``collect`` tool.
- All usage options can be found by using the following command:
.. code-block:: none

7
doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst
View File

@ -138,8 +138,11 @@ User Account Types
- **sudo group** - provides sudo all capabilities.
- **sys_protected group** - provides access to 'collect'
tool for collecting system diagnostic info.
- **sys_protected group** - provides access to ``collect`` tool
for collecting system diagnostic info.
.. note::
The ``collect`` tool also requires sudo capability.
- **root group** - provides read access to log files.