Skip to content

Proxy variables for sidecar container #56917

Open
@baskakkk

Description

@baskakkk

Helm Chart Version

1.1.0 and above

What step the error happened?

Upgrading the Platform or Helm Chart

Relevant information

I have airbyte 1.1.0 deployed in k8s with helm chart
When creating a new connection, a pod with the name "ce-appsflyer-check-..." is raised in which there are two containers (main, connector-sidecar)

These two containers do not have access to the Internet and cannot upload data, they need to specify a proxy, but I don’t know how to do this.

In the airbyte web interface it shows an error 504, the logs for the "ce-appsflyer-check-..." pod are below:

I specify the variables HTTP_PROXY, HTTPS_PROXY, NO_PROXY, http_proxy, https_proxy, no_proxy in .Values.global.env_vars, however they are not transferred to these containers, but these variables are passed to other components without problems

if you need additional information, I am ready to provide

Relevant log output

2024-10-29T11:08:18.914177364Z main INFO Loading mask data from '/seed/specs_secrets_mask.yaml
2024-10-29 11:08:24 INFO i.m.c.e.DefaultEnvironment():168 - Established active environments: [k8s, cloud, worker-v2, control-plane, oss, local-secrets]
2024-10-29 11:08:27 INFO i.a.c.ApplicationKt(main):20 - Context started
2024-10-29 11:08:27 INFO i.a.c.ApplicationKt(main):21 - 6952094558.00 ns/exec (total: 6.95s, 1 executions)
2024-10-29 11:08:28 INFO i.a.c.ApplicationKt(main):28 - Sidecar created
2024-10-29 11:08:28 INFO i.a.c.ApplicationKt(main):29 - 4021543447.00 ns/exec (total: 8.04s, 2 executions)
2024-10-29 11:08:29 INFO i.a.c.i.LineGobbler(voidCall):166 -
2024-10-29T11:08:29.538501209Z pool-5-thread-1 ERROR Recursive call to appender SecretMaskRewrite
2024-10-29 11:08:30 INFO i.a.c.i.LineGobbler(voidCall):166 - ----- START CHECK -----
2024-10-29 11:08:30 INFO i.a.c.i.LineGobbler(voidCall):166 -
2024-10-29 11:08:30 WARN c.a.l.CommonsLog(warn):113 - JAXB is unavailable. Will fallback to SDK implementation which may be less performant.If you are using Java 9+, you will need to include javax.xml.bind:jaxb-api as a dependency.
2024-10-29 11:14:59 WARN i.a.c.HeartbeatMonitor$HeartbeatTask(handleHeartbeatException):97 - Cancelling job, workload is in a terminal state
io.airbyte.workload.api.client.generated.infrastructure.ClientException: Client error : 410 Gone {"message":"Heartbeat a workload in a terminal state"}
at io.airbyte.workload.api.client.generated.WorkloadApi.workloadHeartbeat(WorkloadApi.kt:437) ~[io.airbyte.airbyte-api-workload-api-1.1.0.jar:?]
at io.airbyte.connectorSidecar.HeartbeatMonitor$HeartbeatTask.run(HeartbeatMonitor.kt:84) ~[io.airbyte-airbyte-connector-sidecar-1.1.0.jar:?]
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[?:?]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
2024-10-29 11:14:59 WARN i.a.c.ConnectorWatcher(waitForConnectorOutput):96 - Heartbeat indicates that the workload is in a terminal state, exiting process
2024-10-29 11:14:59 INFO i.a.c.ConnectorWatcher(exitInternalError):221 - Deliberately exiting process with code 1.
2024-10-29 11:14:59 WARN c.v.l.l.Log4j2Appender(close):108 - Already shutting down. Cannot remove shutdown hook.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions