Loki-logger pod now expects some new env variables when running in OpenShift:
LOKI_INSTALL_TYPE - this must be dev or openshift
TLS_CERT_FILE - must be specified for openshift
TLS_KEY_FILE - must be specified for openshift
LOG_TYPE - must be specified for openshift and can be application, infrastructur or audit - defaults to application if not specified
TLS_CERT_FILE and TLS_KEY_FILE can be get from the secret "logging-loki-querier-http" in the "openshift-logging" namespace on the openshift cluster where the loki instance has been installed.
Proposed Solution
1.. Update the install script to copy the secret "logging-loki-querier-http" from the "openshift-logging" namespace to the kubeflow namespace in the core cluster
Shadow pod controller gets also the env variable LOKI_INSTALL_TYPE, and configure the pod template for the Loki logger to pass the LOKI_INSTALL_TYPE flag.
if LOKI_INSTALL_TYPE ==openshift, it configures the pod template to get the certs from the secret "logging-loki-querier-http" in the kubeflow namespace
Feature Description
Loki-logger pod now expects some new env variables when running in OpenShift:
LOKI_INSTALL_TYPE
- this must bedev
oropenshift
TLS_CERT_FILE
- must be specified for openshiftTLS_KEY_FILE
- must be specified for openshiftLOG_TYPE
- must be specified for openshift and can beapplication
,infrastructur
oraudit
- defaults toapplication
if not specifiedTLS_CERT_FILE and TLS_KEY_FILE can be get from the secret "logging-loki-querier-http" in the "openshift-logging" namespace on the openshift cluster where the loki instance has been installed.
Proposed Solution
1.. Update the install script to copy the secret "logging-loki-querier-http" from the "openshift-logging" namespace to the
kubeflow
namespace in the core clusterLOKI_INSTALL_TYPE
, and configure the pod template for the Loki logger to pass theLOKI_INSTALL_TYPE
flag.LOKI_INSTALL_TYPE ==openshift
, it configures the pod template to get the certs from the secret "logging-loki-querier-http" in the kubeflow namespaceWant to contribute?
Additional Context
No response