agentdanger commented on issue #29444:
URL: https://github.com/apache/airflow/issues/29444#issuecomment-1452826643
I was able to solve this issue by installing 1.8 with the configured yaml
file.
My namespace for this implementation was colosseum.
I had a custom yaml filed
agentdanger commented on issue #29444:
URL: https://github.com/apache/airflow/issues/29444#issuecomment-1452631098
I'm caveating my "no issue" suggestion above. I'm currently working through
bugs on the git-sync but those could be my own doing. My work around was able
to solve the
agentdanger commented on issue #29444:
URL: https://github.com/apache/airflow/issues/29444#issuecomment-1452620409
I was able to resolve this issue.
Upgrading also refers to upgrading the existing 1.8 instance. You have to
follow @potiuk suggestion within the release notes.
agentdanger commented on issue #29444:
URL: https://github.com/apache/airflow/issues/29444#issuecomment-1452576191
I get the issue when I do a helm upgrade to install the custom values.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
agentdanger commented on issue #29444:
URL: https://github.com/apache/airflow/issues/29444#issuecomment-1452573578
I can recreate this issue by doing a fresh install using the 1.8 helm image
"my-airflow", in a fresh namespace on kubernetes, and customizing the
values.yaml to attempt to
