Description of problem:
As mentioned in the doc when we set the var openshift_logging=project_name
the components get deployed to the project openshift-logging project instead of the "project_name" mentioned.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set the following vars in inventory:
2. run the playbook:
ansible-playbook -i hosts /usr/share/ansible/openshift-ansible/playbooks/openshift-logging/config.yml -vvv | tee logging.txt
Actual results: The resources are deployed in openshift-logging
Expected results: The resources should be deployed in logging
Additional info: If the project for logging cannot be changed, then let me know, I will raise a doc bug.
This is a documentation issue. The correct variable is `openshift_logging_namespace`. Note we encourage use of the current default 'openshift-logging' as this will be the only project where cluster logging will be deployable in 4.x
Actually reviewing further, there is no way to modify the namespace which was originally documented here https://bugzilla.redhat.com/show_bug.cgi?id=1588290. The roles will try to use an existing namespace otherwise deploy to 'openshift-logging'. The documents should be modified to remove that particular row from the table and simply state what the default is.
Removed `openshift_logging` from the variable table and noted in Deploy EFK that all logging components are " deployed to the project `openshift-logging`."
It would be really nice if the name of the namespace could be customized.
A lot of customer have tooling and automation around this where they now have to manage a mix of upgraded clusters with the old namespace and the new one
The logging roles include logic to check if logging is deployed to a namespace other then 'openshift-logging' and will make updates and changes using what it finds. New deployments will only be installed to 'openshift-logging'. Additionally, there is planned work for 4.x to migrate existing logging deployments to the 'openshift-logging' namespace during a 3.11 to 4.x upgrade.
Changes are live: