Status of testing of Apache Airflow Helm Chart 1.18.0rc2

[jedcunningham]

We are kindly requesting that contributors to Apache Airflow Helm Chart 1.18.0rc2 help test the RC.

Please let us know by commenting if the issue is addressed in the latest RC.

• Change default executor in pod template to support executor parameter in task (re-uploaded) (#49433):
  @ihnokim
• fix: allow configmap and secret references in the apiServer.env field (#51191): @romsharon98 @LucasRoe
  sler
  Linked issues:
  • incorrect helm chart validation for apiServer.env field (#51190)
• Use merged to render airflow.cfg and include computed defaults (#51828): @bdsoha
• Update service name for port-forward of Airflow GUI (#51945): @gsingh935
• Update Helm Chart docs with 3.0 support (#52132): @kaxil
• Helm: add custom annotations to jwt secret (#52166): @Aakcht
• Use api-server instead of webserver in chart NOTES.txt for Airflow 3.0+. (#52194): @simi
• fix: correct JWT secret name to match deployment environment (#52268): @junminahn
• Use api secret_key for airflow 3.0+ instead of webserver secret_key (#52269): @albundy83
• Fix for fernetkey and add test of its value (#52977): @albundy83
• fix: allow valuesFrom in gitSync.env (#50228): @mo-rieger

Thanks to all who contributed to the release (probably not a complete list!):
@simi @Aakcht @eladkal @bdsoha @romsharon98 @ihnokim @junminahn @jedcunningham @LucasRoesler @jscheffl @kaxil @albundy83 @gsingh935 @mo-rieger

[bdsoha]

• Use merged to render airflow.cfg and include computed defaults #51828

[simi]

• Use api-server instead of webserver in chart NOTES.txt for Airflow 3.0+. #52194

[Aakcht]

• Helm: add custom annotations to jwt secret #52166

[LucasRoesler]

• fix: allow configmap and secret references in the apiServer.env field #51191

[albundy83]

Can someone help me to deploy this release ?
How should I install it on my env ?

[albundy83]

Ok sorry, I find the trick, url is https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.18.0rc2 and version is 1.18.0 not 1.18.0rc2

[albundy83]

• Use api secret_key for airflow 3.0+ instead of webserver secret_key (#52269)
  And fix Missing api secret_key capabilities to replace webserver for 3.0+ #52267

[albundy83]

I have a question about this one #52268
I really think that all Secrets should have been renamed with the airflow.fullname or .Release.Name inside or just like jwt Secret with {{ include "jwt_secret" . }}.

Maybe @jedcunningham you could decide which one we use :) ?

And also jwt Secret has the bug b64enc twice, we must also fix this
I can prepare pull requests for all this.

[jedcunningham]

@albundy83 we should be using airflow.fullname. I wonder if we are missing some test coverage to make sure we are actually. Some prior art here: #31066

One thing to be mindful of is our helm pre-install hooks, we can't really rename those.

I don't feel this is a blocker for 1.18.0 though.

Does the double b64 for jwt secret cause any issues? My immediate thought is we can fix that in the next release.

[albundy83]

It's not a blocker either maybe we could look into it for the next release, to keep things consistent.

As for the double b64, that's not a blocker either, the content is not important as long as the word is long and hard to guess :)

[prakass1]

Tested this.

• Update service name for port-forward of Airflow GUI: @gsingh935

[prakass1]

I have noticed an issue with the default Fernet key and erroring when testing the chart:

How to Replicate:

• Run airflow on kubernetes:

helm repo add apache-airflow-dev https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.18.0rc1/
helm repo update
helm install airflow apache-airflow-dev/airflow --namespace airflow-dev-test

• port forward the api-server: kubectl port-forward svc/airflow-api-server 8080:8080 --namespace airflow-dev-test to access the UI.
• Add a Variable and see 500 Internal Server Error:

Operating System:

MacOS

Error Message:

File "/home/airflow/.local/lib/python3.12/site-packages/anyio/backends/asyncio.py", line 967, in run
result = context.run(func, *args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/api_fastapi/core_api/routes/public/variables.py", line 187, in post_variable
Variable.set(**post_body.model_dump(), session=session)
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/models/variable.py", line 235, in set
session.add(Variable(key=key, val=stored_value, description=description))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 4, in init
File "/home/airflow/.local/lib/python3.12/site-packages/sqlalchemy/orm/state.py", line 481, in initialize_instance
with util.safe_reraise():
^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 70, in exit
compat.raise(
File "/home/airflow/.local/lib/python3.12/site-packages/sqlalchemy/util/compat.py", line 211, in raise
raise exception
File "/home/airflow/.local/lib/python3.12/site-packages/sqlalchemy/orm/state.py", line 479, in initialize_instance
return manager.original_init(*mixed[1:], **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/models/variable.py", line 61, in init
self.val = val
^^^^^^^^
File "", line 1, in set
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/models/variable.py", line 93, in set_val
fernet = get_fernet()
^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/models/crypto.py", line 90, in get_fernet
raise AirflowException(f"Could not create Fernet object: {value_error}")
airflow.exceptions.AirflowException: Could not create Fernet object: Fernet key must be 32 url-safe base64-encoded bytes.

Are there any solutions already thought for this?, also probably providing the fernetKey in the values.yaml may be a workaround I suppose.