La diffusion des journaux ne fonctionne pas dans les configurations proxy

Description

La redirection de journal ne fonctionne pas dans les configurations de proxy car les variables d’environnement de proxy n’ont pas été définies dans les pods de journalisation.

Solution

1. Définissez les variables d'environnement http_proxy , https_proxy et no_proxy . Exemple :

   export http_proxy=http://<proxy>:3128
   export https_proxy=http://<proxy>:3128
   export no_proxy=<fqdn>,.<fqdn>,10.0.0.0/8,kerberossql.autosuitead.local,kerberospostgres.AUTOSUITEAD.LOCAL,rook-ceph-rgw-rook-ceph.rook-ceph.svc.cluster.local,localhost,127.0.0.1,kubernetes,kubernetes.default,kubernetes.default.svc,kubernetes.default.svc.cluster,kubernetes.default.svc.cluster.local,.svc,.svc.cluster,.svc.cluster.local,.svc.cluster.local.,.uipath.svc.cluster.local,argocd-repo-server,istiod.istio-system.svc,logging-operator-logging-fluentd.logging.svc.cluster.local,.local,.cluster,ai-helper-svc,ai-pkgmanager-svc,ai-deployer-svc,ai-appmanager-svc,ai-trainer-svc,studioweb-backend,studioweb-frontend,studioweb-typecache

2. Exécutez le script suivant qui ingère les variables d'environnement dans les pods de journalisation et les redémarre.

   #!/bin/bash
   
   set -euo pipefail
   
   APP_NAME="logging"
   NAMESPACE="argocd"
   HTTP_PROXY="${http_proxy:-}"
   HTTPS_PROXY="${https_proxy:-}"
   NO_PROXY="${no_proxy:-}"
   
   # Create a temporary JSON patch
   PATCH_FILE=$(mktemp)
   
   cat > "$PATCH_FILE" <<EOF
   {
     "spec": {
       "source": {
         "helm": {
           "parameters": [
             { "name": "logging-operator.env[0].name", "value": "http_proxy" },
             { "name": "logging-operator.env[0].value", "value": "${HTTP_PROXY}" },
             { "name": "logging-operator.env[1].name", "value": "https_proxy" },
             { "name": "logging-operator.env[1].value", "value": "${HTTPS_PROXY}" },
             { "name": "logging-operator.env[2].name", "value": "no_proxy" },
             { "name": "logging-operator.env[2].value", "value": "${NO_PROXY}" },
   
             { "name": "logging-operator.logging.fluentd.envVars[0].name", "value": "http_proxy" },
             { "name": "logging-operator.logging.fluentd.envVars[0].value", "value": "${HTTP_PROXY}" },
             { "name": "logging-operator.logging.fluentd.envVars[1].name", "value": "https_proxy" },
             { "name": "logging-operator.logging.fluentd.envVars[1].value", "value": "${HTTPS_PROXY}" },
             { "name": "logging-operator.logging.fluentd.envVars[2].name", "value": "no_proxy" },
             { "name": "logging-operator.logging.fluentd.envVars[2].value", "value": "${NO_PROXY}" },
   
             { "name": "logging-operator.logging.fluentbit.envVars[0].name", "value": "http_proxy" },
             { "name": "logging-operator.logging.fluentbit.envVars[0].value", "value": "${HTTP_PROXY}" },
             { "name": "logging-operator.logging.fluentbit.envVars[1].name", "value": "https_proxy" },
             { "name": "logging-operator.logging.fluentbit.envVars[1].value", "value": "${HTTPS_PROXY}" },
             { "name": "logging-operator.logging.fluentbit.envVars[2].name", "value": "no_proxy" },
             { "name": "logging-operator.logging.fluentbit.envVars[2].value", "value": "${NO_PROXY}" }
           ]
         }
       }
     }
   }
   EOF
   
   # Patch the Argo CD Application
   kubectl patch application "$APP_NAME" -n "$NAMESPACE" --type merge --patch-file "$PATCH_FILE"
   
   # Cleanup
   rm -f "$PATCH_FILE"
   
   echo "Patched Argo CD Application '$APP_NAME' with proxy parameters."
   echo "Restarting logging pods..."
   
   kubectl  rollout restart deploy/logging-logging-operator -n logging
   kubectl  rollout restart sts/logging-fluentd -n logging
   kubectl  rollout restart ds/logging-fluentbit  -n logging
   
   echo "Rollout restart completed"