SvenThies

Same here! It seems that within the Spark context, a different DNS resolver is used. We currently did an ugly workaround by giving the container a fixed IP and reference...

Hey @Fokko, thanks for the suggestions. Unfortunately, it doesn't work. We tried the following ``` spark.sql.extensions org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions spark.sql.catalog.default org.apache.iceberg.spark.SparkCatalog spark.sql.catalog.default.catalog-impl org.apache.iceberg.rest.RESTCatalog spark.sql.catalog.default.uri http://rest:8181 spark.sql.catalog.default.io-impl org.apache.iceberg.aws.s3.S3FileIO spark.sql.catalog.default.warehouse s3://dev-customer-analytics/ spark.sql.catalog.default.s3.endpoint http://minio:9000 spark.sql.catalog.default.s3.path-style-access...

@wenchajun what would be the plan here? Otherwise, when using `flushSeconds`, the behaviour is as expected and the issue can be closed.

Hey, I've created a [PR](https://github.com/fluent/fluent-operator/pull/1223) which will close this issue.

@vi4vikas is this still an issue? Also with an update on the most recent version? Otherwise, can the issue be closed?

@max-allan can you confirm that this issue is closed with #1199. Can this issue be closed?

Hey @onap4105, I followed your instruction and tried to reproduce the issue. For me, everything worked well: Adding this into values.yaml under fluentbit section: ``` fluentbit: # initContainers test run...

@sugaf1204, the configuration will be built always in the same way, as #1106 describes. The execution of filters is then also always the same. So the order is controlled by...

@Karthika-Pingali does this resolve this issue? Can it be closed?

Hello @jkrbharath, can you provide more information? What is the release you use? How did you install it exactly via helm (cmd and/or values.yaml)? Thx!