This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71
stars
64
forks
source link
feat: (IAC-397) Add password setting support for kibana new user logadm #263
viya4-monitoring-kubernetes added a new user 'logadm' as a day-to-day user for log monitoring for cluster administrators. Changes in this PR help user in setting password for this new user logadm.
To set the password for the logadm user, set the V4M_KIBANA_LOGADM_PASSWORD variable in ansible-vars file. If no password has been set for the logadm user, but a password has been set for the admin user (by using the V4M_KIBANA_PASSWORD variable), then that password is used for the logadm user also. If neither password has been set, random passwords are generated for these accounts. These random passwords are displayed in the log messages generated during the deployment process.
Tests:
Following scenarios were verified. See internal ticket for details.
Scenario 1: set password for logadm -- verify logadm can access dashboard with the set password
Scenario 2: Do not set password for logadm but set password for admin user -- verify logadm can access dashboard with the password set for admin user
Scenario 3: Do not set password for logadm and admin user -- verify password is randomly generated and output in the logs
Changes:
viya4-monitoring-kubernetes added a new user 'logadm' as a day-to-day user for log monitoring for cluster administrators. Changes in this PR help user in setting password for this new user logadm.
To set the password for the
logadmuser, set theV4M_KIBANA_LOGADM_PASSWORDvariable in ansible-vars file. If no password has been set for thelogadmuser, but a password has been set for theadminuser (by using theV4M_KIBANA_PASSWORDvariable), then that password is used for thelogadmuser also. If neither password has been set, random passwords are generated for these accounts. These random passwords are displayed in the log messages generated during the deployment process.Tests:
Following scenarios were verified. See internal ticket for details.