Hi team, I am currently trying to deprecate

minio

from the

gke k8s airbyte

deployment and only use

gcs

for logging. When I remove the

aws/s3

specific envars from the worker pod I get the following error:

Appender java.lang.IllegalStateException: No factory method found for class com.van.logging.log4j2.Log4j2Appender                                                                                                                             
        at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.findFactoryMethod(PluginBuilder.java:234)                                                                                                                          
        at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:134

As far as I can tell, this is due to the the logging plugin unable to find the directory to log in, are there any other envar I need to set? These are the ones I removed from the

worker.yaml envars

- name: S3_LOG_BUCKET
  valueFrom:
    configMapKeyRef:
      name: airbyte-env
      key: S3_LOG_BUCKET
- name: S3_LOG_BUCKET_REGION
  valueFrom:
    configMapKeyRef:
      name: airbyte-env
      key: S3_LOG_BUCKET_REGION
- name: AWS_ACCESS_KEY_ID
  valueFrom:
    secretKeyRef:
      name: airbyte-secrets
      key: AWS_ACCESS_KEY_ID
- name: AWS_SECRET_ACCESS_KEY
  valueFrom:
    secretKeyRef:
      name: airbyte-secrets
      key: AWS_SECRET_ACCESS_KEY
- name: S3_MINIO_ENDPOINT
  valueFrom:
    configMapKeyRef:
      name: airbyte-env
      key: S3_MINIO_ENDPOINT
- name: S3_PATH_STYLE_ACCESS
  valueFrom:
    configMapKeyRef:
      name: airbyte-env
      key: S3_PATH_STYLE_ACCESS

Hey @Shah Newaz Khan did you manage to fix this? We are getting the same error.

@Filip Rodik did u manage to get past this ?

@Krishna Elangovan how are you deploying - Kustomize or Helm chart?

r u guys on the latest helm chart version?

using 40.33