Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

Hello,

it could also be:

{{- define "jwt_secret" -}}
  {{- default (printf "%s-jwt_secret" (include "airflow.fullname" .)) .Values.jwtSecretName }}
{{- end }}

As defined for webserver_secret_key_secret:

Hello,

it could also be:

{{- define "jwt_secret" -}}
  {{- default (printf "%s-jwt_secret" (include "airflow.fullname" .)) .Values.jwtSecretName }}
{{- end }}

As defined for webserver_secret_key_secret:

That works too, but my main intention is to reuse the same variable jwt_secret, defined in the helper file, in both the deployment and secret files to ensure consistency in the secret name. We can discuss the best way to define the variable separately, whether it's using airflow.fullname or .Release.Name.

@junminahn can you also fix the failing test, as the name has been fixed now? Thanks.

@junminahn can you also fix the failing test, as the name has been fixed now? Thanks.

I've updated the test file as needed. Could you please approve the pending workflows?

@jedcunningham Thanks for approving the workflows; all checks are passing now. Would you mind merging this PR? Appreciate it!

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

Thanks @junminahn! Congrats on your first commit 🎉