Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-8076

getAWSCredentialFromCluster failed as there isn't aws-cred in kube-system

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Log QE
    • None
    • Quality / Stability / Reliability
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • NEW
    • NEW
    • If Release Note Needed, Set a Value
    • Logging - Sprint 279, Logging - Sprint 280

      Some test case failed on the cluster, ipi-on-aws/versioned-installer-customer_vpc-
      disconnected_private_cluster-usgov-ci 4.20.0-0.nightly-2025-10-30-114955

      Author:qitang-CPaasrunOnly-Medium-76115-Controlling the flow rate per destination to selected outputs LokiStack [Serial][Slow]
      Author:kbharti-CPaasrunOnly-Medium-61435-Validate AlertManager support for User-workload monitoring[Serial]
      Author:qitang-CPaasrunOnly-ConnectedOnly-High-76729-LokiStack 1x.pico Support[Serial]
      Author:qitang-CPaasrunOnly-Critical-68961-Forward logs to OTEL collector

      As there isn't secret/aws-cred in kube-system.

      How to fix it?
      1) use secret/image-registry-private-configuration -o yaml
      2) honer the AWS_SHARED_CREDENTIALS_FILE as what we did for AWS STS

              Unassigned Unassigned
              rhn-support-anli Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: