@kapa.ai why is airbyte server is in a crashloopbackoff status ? here are the logs i see

2025-02-06 09:20:44,398 [main]	INFO	i.m.c.e.DefaultEnvironment(<init>):168 - Established active environments: [control-plane]
2025-02-06 09:20:53,282 [main]	INFO	c.z.h.HikariDataSource(<init>):79 - HikariPool-1 - Starting...
2025-02-06 09:20:53,491 [main]	INFO	c.z.h.HikariDataSource(<init>):81 - HikariPool-1 - Start completed.
2025-02-06 09:20:56,779 [main]	INFO	i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):155 - Waiting for temporal server...
2025-02-06 09:20:56,779 [main]	WARN	i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):166 - Waiting for namespace default to be initialized in temporal...
2025-02-06 09:21:00,683 [main]	INFO	i.t.s.WorkflowServiceStubsImpl(<init>):86 - Created WorkflowServiceStubs for channel: ManagedChannelOrphanWrapper{delegate=ManagedChannelImpl{logId=1, target=airbyte-temporal:7233}}
2025-02-06 09:21:08,488 [main]	INFO	i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):183 - Temporal namespace default initialized!
2025-02-06 09:21:08,682 [main]	WARN	i.a.m.l.MetricClientFactory(initialize):72 - MetricClient was not recognized or not provided. Accepted values are `datadog` or `otel`. 
2025-02-06 09:21:09,102 [main]	INFO	i.a.f.ConfigFileClient(<init>):113 - path /flags does not exist, will return default flag values
2025-02-06 09:21:10,982 [main]	INFO	c.z.h.HikariDataSource(<init>):79 - config-pool - Starting...
2025-02-06 09:21:10,984 [main]	INFO	c.z.h.HikariDataSource(<init>):81 - config-pool - Start completed.
2025-02-06 09:21:12,087 [main]	INFO	i.a.c.p.ActorDefinitionVersionHelper(<init>):54 - ActorDefinitionVersionHelper initialized with override provider: ConfigurationDefinitionVersionOverrideProvider
2025-02-06 09:21:13,421 [main]	INFO	i.a.c.s.RemoteDefinitionsProvider(<init>):76 - Creating remote definitions provider for URL '<https://connectors.airbyte.com/files/>' and registry 'OSS'...
2025-02-06 09:21:19,197 [main]	INFO	i.t.s.WorkflowServiceStubsImpl(<init>):86 - Created WorkflowServiceStubs for channel: ManagedChannelOrphanWrapper{delegate=ManagedChannelImpl{logId=5, target=airbyte-temporal:7233}}
2025-02-06 09:21:19,208 [main]	INFO	i.a.c.r.c.ConnectorRolloutClient(<init>):34 - ConnectorRolloutService constructor
2025-02-06 09:21:19,506 [main]	INFO	i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.netty'
2025-02-06 09:21:20,812 [main]	INFO	i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'ERROR' for logger: 'com.zaxxer.hikari'
2025-02-06 09:21:20,813 [main]	INFO	i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.grpc'
2025-02-06 09:21:20,815 [main]	INFO	i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.temporal'
2025-02-06 09:21:20,816 [main]	INFO	i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'ERROR' for logger: 'com.zaxxer.hikari.pool'
2025-02-06 09:21:20,817 [main]	INFO	i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.fabric8.kubernetes.client'

Based on the logs you've provided, it appears that the Airbyte server is not in a CrashLoopBackOff status. The logs show that the server is initializing and connecting to various components. However, there are a few potential issues that could lead to problems: 1. Temporal connection: The logs show that the server is waiting for the Temporal server to be ready and for the default namespace to be initialized. This process seems to complete successfully, as indicated by the line:

2025-02-06 09:21:08,488 [main] INFO i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):183 - Temporal namespace default initialized!

2. Metric Client: There's a warning about the MetricClient not being recognized or provided:

2025-02-06 09:21:08,682 [main] WARN i.a.m.l.MetricClientFactory(initialize):72 - MetricClient was not recognized or not provided. Accepted values are `datadog` or `otel`.

This isn't necessarily causing a crash, but it might affect metric collection. 3. Configuration flags: The logs indicate that the

/flags

path doesn't exist, so default flag values will be used:

2025-02-06 09:21:09,102 [main] INFO i.a.f.ConfigFileClient(<init>):113 - path /flags does not exist, will return default flag values

This could potentially cause issues if specific configurations are required for your setup. The logs you've provided don't show any critical errors that would cause a CrashLoopBackOff status. If the server is indeed in CrashLoopBackOff, there might be additional logs after the ones you've shared that could provide more information about the cause. To troubleshoot further, you could: 1. Check for any logs that come after the ones you've shared, especially looking for any ERROR level logs. 2. Verify that all required services (like the database and Temporal) are running and accessible. 3. Check the Kubernetes events for the pod to see if there are any issues with scheduling or resource constraints. If you're still facing issues, you might want to check out the [Airbyte Troubleshooting Guide](https://docs.airbyte.com/operator-guides/troubleshooting/) for more detailed steps on diagnosing and resolving common problems.