michaelefisher
commented
9 months ago We are seeing this on the latest chart without external minio set. We have no values outside of the default chart-supplised values (at least in terms of logging configs).
We are also no longer seeing logs printed in the UI. Unsure if this is totally related, but it only started on the latest chart.
We're on GKE, so we're still seeing all of our logs in Stackdriver/Google Logging, of course.
Here's our configmap - nothing secret in there, so I'm just sharing the entire thing:
kubectl -n airbyte get configmap cta-airbyte-airbyte-env -o yaml
apiVersion: v1
data:
ACTIVITY_INITIAL_DELAY_BETWEEN_ATTEMPTS_SECONDS: ""
ACTIVITY_MAX_ATTEMPT: ""
ACTIVITY_MAX_DELAY_BETWEEN_ATTEMPTS_SECONDS: ""
AIRBYTE_API_HOST: cta-airbyte-airbyte-api-server-svc:80
AIRBYTE_EDITION: community
AIRBYTE_VERSION: 0.50.44
API_URL: /api/v1/
AUTO_DETECT_SCHEMA: "true"
CONFIG_API_HOST: http://cta-airbyte-airbyte-server-svc:8001
CONFIG_ROOT: /configs
CONFIGS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION: 0.35.15.001
CONNECTOR_BUILDER_API_HOST: cta-airbyte-airbyte-connector-builder-server-svc:80
CONNECTOR_BUILDER_API_URL: /connector-builder-api
CONNECTOR_BUILDER_SERVER_API_HOST: http://cta-airbyte-airbyte-connector-builder-server-svc:80
CONTAINER_ORCHESTRATOR_IMAGE: ""
CRON_MICRONAUT_ENVIRONMENTS: control-plane
DATA_DOCKER_MOUNT: airbyte_data
DATABASE_DB: db-airbyte
DATABASE_HOST: airbyte-db-svc
DATABASE_PORT: "5432"
DATABASE_URL: jdbc:postgresql://airbyte-db-svc:5432/db-airbyte
DB_DOCKER_MOUNT: airbyte_db
GCS_LOG_BUCKET: ""
GOOGLE_APPLICATION_CREDENTIALS: ""
INTERNAL_API_HOST: cta-airbyte-airbyte-server-svc:8001
JOB_MAIN_CONTAINER_CPU_LIMIT: ""
JOB_MAIN_CONTAINER_CPU_REQUEST: ""
JOB_MAIN_CONTAINER_MEMORY_LIMIT: ""
JOB_MAIN_CONTAINER_MEMORY_REQUEST: ""
JOBS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION: 0.29.15.001
KEYCLOAK_DATABASE_URL: jdbc:postgresql://airbyte-db-svc:5432/db-airbyte?currentSchema=keycloak
KEYCLOAK_INTERNAL_HOST: localhost
LAUNCHER_MICRONAUT_ENVIRONMENTS: control-plane,oss
LOCAL_ROOT: /tmp/airbyte_local
MAX_NOTIFY_WORKERS: "5"
METRIC_CLIENT: ""
MICROMETER_METRICS_ENABLED: "false"
MICROMETER_METRICS_STATSD_FLAVOR: datadog
OTEL_COLLECTOR_ENDPOINT: ""
RUN_DATABASE_MIGRATION_ON_STARTUP: "true"
S3_LOG_BUCKET: airbyte-dev-logs
S3_LOG_BUCKET_REGION: us-west-2
S3_MINIO_ENDPOINT: http://airbyte-minio-svc:9000
S3_PATH_STYLE_ACCESS: "true"
SEGMENT_WRITE_KEY: XXXXXXXXX
SHOULD_RUN_NOTIFY_WORKFLOWS: "true"
STATE_STORAGE_MINIO_BUCKET_NAME: state-storage
STATE_STORAGE_MINIO_ENDPOINT: http://airbyte-minio-svc:9000
STATSD_HOST: localhost
STATSD_PORT: "8125"
TEMPORAL_HOST: cta-airbyte-temporal:7233
TEMPORAL_WORKER_PORTS: 9001,9002,9003,9004,9005,9006,9007,9008,9009,9010,9011,9012,9013,9014,9015,9016,9017,9018,9019,9020,9021,9022,9023,9024,9025,9026,9027,9028,9029,9030,9031,9032,9033,9034,9035,9036,9037,9038,9039,9040
TRACKING_STRATEGY: segment
WEBAPP_URL: http://cta-airbyte-airbyte-webapp-svc:80
WORKER_ENVIRONMENT: kubernetes
WORKER_LOGS_STORAGE_TYPE: MINIO
WORKER_STATE_STORAGE_TYPE: MINIO
WORKERS_MICRONAUT_ENVIRONMENTS: control-plane
WORKFLOW_FAILURE_RESTART_DELAY_SECONDS: ""
WORKLOAD_API_HOST: http://localhost
WORKLOAD_LAUNCHER_PARALLELISM: "10"
WORKSPACE_DOCKER_MOUNT: airbyte_workspace
WORKSPACE_ROOT: /workspace
kind: ConfigMap
metadata:
annotations:
helm.sh/hook: pre-install,pre-upgrade
helm.sh/hook-weight: "-1"
creationTimestamp: "2024-01-25T17:37:22Z"
labels:
app.kubernetes.io/instance: cta-airbyte
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: airbyte
app.kubernetes.io/version: 0.50.44
helm.sh/chart: airbyte-0.50.55
name: cta-airbyte-airbyte-env
namespace: airbyte
resourceVersion: "164567339"
uid: 39e8b2c2-cade-4e2b-b011-38428fd3905c
leonardo-lages-hyperflow
hengzi52125
marcosmarxm
Helm Chart Version
0.50.44
What step the error happened?
During the Sync
Revelant information
I want to use external MINIO. Here is my values.yaml
When I sync a connection, airbyte-server pod and airbyte-worker pod all throw the error: "java.lang.IllegalArgumentException: Cannot create enum from ${env:S3_LOG_BUCKET_REGION} value!"
So, I added "global.logs.s3.bucketRegion" into the values.yaml.
airbyte-server and airbyte-worker throw error: java.lang.IllegalStateException: Only one of Region or EndpointConfiguration may be set.
Relevant log output