Protokollstreaming funktioniert nicht in Proxy-Setups

Beschreibung

Die Protokollweiterleitung funktioniert nicht in Proxy-Setups, da die Proxy-Umgebungsvariablen nicht in den Protokollierungs-Pods festgelegt wurden.

Lösung

1. Legen Sie die Umgebungsvariablen http_proxy , https_proxy und no_proxy fest. Beispiel:

   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. Führen Sie das folgende Skript aus, das die Umgebungsvariablen in die Protokollierungs-Pods aufnimmt und neu startet.

   #!/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"