Does it make sense for the triggerer to have persistence enabled in k8s while using remote logging?

[slmg]

Hi, is the below appropriate? Setting

• persistence: false renders a Deployment
• persistence: true renders a StatefulSet defining a logs PVC.

As I am using remote logging, it would feel redundant to persists logs into a volume. Butt since I am unfamiliar with the internals of the triggerer, I am wondering if I missed anything else which would justify to set persistence: true?

Thanks

helm chart version: 1.10.0

values.yaml

# Config settings to go into the mounted airflow.cfg
config:
  logging:
    remote_logging: "True"
    remote_base_log_folder: s3://bucket/path/to/logs

triggerer:
  persistence:
    enabled: false

[potiuk]

No. It's OK to disable it in this case.

[slmg]

Thanks. Should I transfer it into an issue? It could be reasonable to disable persistence if remote logging is enabled then.

[potiuk]

Better if you transfer it into PR.

[akhilesh-minfy]

Hey @potiuk I would be happy if you can share me the answer for this
im using logging like that provided by values
logs:
persistence:
enabled: true
existingClaim: airflow-logs-longhorn-pvc

so can i disable
triggerer:
persistence:
enabled: false