-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitCredentialsSecret doesn't follow RFC 1123 specification - also not in nightly build #500
Comments
Could you attach the Pod description (in yaml) for the airflow scheduler or webserver, showing (at least) the image section and the env section (with values changed where appropriate)? (for the failing case, not the workaround) |
That internal variable |
I asked our ops engineers a few times, but will do it again, to make sure we have the correct nightly, coming back to you about it |
@adwk67 somehow it is working now - something went wrong on our side. Sorry for the discussion. Closing this ticket. |
Just asking for clarification: This used to work in 23.4 and is not working in 23.7 anymore and will be fixed in the next release? If so, shouldn't there be an information on the 23.7 release notes that there is a known breaking issue for Airflow? |
This was working in 24.3, was broken in 24.7, has since been fixed and is available in the nightly builds. But, yes, you're right: it's a bit confusing so I'll add something to the 24.7 release notes as per your suggestion. |
Affected Stackable version
stackable0.0.0-dev
Affected Apache Airflow version
2.9.3
Current and expected behavior
Current behavior:
With the following cluster configuration; the following error will prevent the webserver and scheduler to start up:
Expected behavior
No error is shown and the webserver and scheduler are starting up.
Fix that is working
Possible solution
It would be nice to to use the podOverrides to be able to start up the airflow cluster
Additional context
Bug already reported: #486
Environment
kubernetes cluster: openshift
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: