Hi team i am trying to deploy airbyte using helm chart of version

0.47.9

on kubernetes. When using this helm chart as it it with postgresql pod deploy in K8, it works. When Using external postrgress we faced

no encryption

on temporal but that is resolved by disabling force ssl on AWS rds. but now we are facing another issue on server/worker/cron error as below

2023-08-17 09:18:15 WARN i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):259 - Waiting for namespace default to be initialized in temporal...
2023-08-17 09:18:17 INFO i.t.s.WorkflowServiceStubsImpl(<init>):86 - Created WorkflowServiceStubs for channel: ManagedChannelOrphanWrapper{delegate=ManagedChannelImpl{logId=37, target=airbyte-temporal:7233}}
2023-08-17 09:18:17 WARN i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):269 - Ignoring exception while trying to request Temporal namespace:
io.grpc.StatusRuntimeException: NOT_FOUND: Namespace default does not exist.

temporal pod is running can someone help

Based on the information provided in the extracts, it seems like you're encountering an issue with the Temporal namespace not being found when deploying Airbyte on Kubernetes using Helm charts with an external PostgreSQL database. From the extracts, it's not entirely clear what could be causing this specific issue. However, there are a few things you could check: 1. Ensure that the namespace you're deploying to in Kubernetes is correctly configured and accessible. You can verify this by running

kubectl get namespaces

to list all available namespaces. 2. Check the configuration of your Helm chart and make sure that the namespace is correctly specified. In the Helm command, this is usually done with the

-n

or

--namespace

flag. 3. Make sure that the Temporal service is correctly configured and running. You can check the status of the pods in the Temporal namespace by running

kubectl get pods -n <temporal-namespace>

. 4. If you're using an external database, ensure that the connection details are correctly specified in your Helm chart configuration. This includes the host, port, username, password, and database name. If the issue persists, it would be helpful to have more information about your specific setup and configuration. This could include the exact Helm command you're using to deploy Airbyte, the contents of your Helm chart configuration (values.yaml), and any error messages or logs from the Airbyte and Temporal pods. Unfortunately, the information provided in the extracts does not include a direct solution to this issue. For more detailed assistance, you might want to consider reaching out to the Airbyte community on their [Slack channel](https://airbytehq.slack.com/archives/C021JANJ6TY) or [forum](https://discuss.airbyte.io).

@kapa.ai all components are deployed in single namespace because we only have access to one namespace on our infrastructure.

New message text here

i checked all namespace in helm chart its set to our own namespace and not default/temporal