hakuno opened a new issue, #34975:
URL: https://github.com/apache/airflow/issues/34975

   ### Apache Airflow version
   
   2.7.2
   
   ### What happened
   
   The cleanup job doesn't work after the upgrade.
   
   The container calls
   ```
   airflow kubernetes cleanup-pods --namespace=airflow
   ```
   But it gets
   ```
   airflow command error: argument GROUP_OR_COMMAND: invalid choice: 
'kubernetes' (choose from 'celery', 'cheat-sheet', 'config', 'connections', 
'dag-processor', 'dags', 'db', 'info', 'jobs', 'kerberos', 'plugins', 'pools', 
'providers', 'roles', 'rotate-fernet-key', 'scheduler', 'standalone', 
'sync-perm', 'tasks', 'triggerer', 'users', 'variables', 'version', 
'webserver'), see help above.
   Usage: airflow [-h] GROUP_OR_COMMAND ...
   
   Positional Arguments:
     GROUP_OR_COMMAND
       
       Groups
         celery         Celery components
         config         View configuration
         connections    Manage connections
         dags           Manage DAGs
         db             Database operations
         jobs           Manage jobs
         pools          Manage pools
         providers      Display providers
         roles          Manage roles
         tasks          Manage tasks
         users          Manage users
         variables      Manage variables
       
       Commands:
         cheat-sheet    Display cheat sheet
         dag-processor  Start a standalone Dag Processor instance
         info           Show information about current Airflow and environment
         kerberos       Start a kerberos ticket renewer
         plugins        Dump information about loaded plugins
         rotate-fernet-key
                        Rotate encrypted connection credentials and variables
         scheduler      Start a scheduler instance
         standalone     Run an all-in-one copy of Airflow
         sync-perm      Update permissions for existing roles and optionally 
DAGs
         triggerer      Start a triggerer instance
         version        Show the version
         webserver      Start a Airflow webserver instance
   
   Optional Arguments:
     -h, --help         show this help message and exit
   ```
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   I deploy with the official Helm Chart.
   
   ### Operating System
   
   Debian GNU/Linux 11 (bullseye)
   
   ### Versions of Apache Airflow Providers
   
   ```
   apache-airflow-providers-amazon==8.7.1
   apache-airflow-providers-celery==3.3.4
   apache-airflow-providers-cncf-kubernetes==7.6.0
   apache-airflow-providers-common-sql==1.7.2
   apache-airflow-providers-daskexecutor==1.0.1
   apache-airflow-providers-docker==3.7.5
   apache-airflow-providers-elasticsearch==5.0.2
   apache-airflow-providers-ftp==3.5.2
   apache-airflow-providers-google==10.9.0
   apache-airflow-providers-grpc==3.2.2
   apache-airflow-providers-hashicorp==3.4.3
   apache-airflow-providers-http==4.5.2
   apache-airflow-providers-imap==3.3.2
   apache-airflow-providers-microsoft-azure==7.0.0
   apache-airflow-providers-mysql==5.3.1
   apache-airflow-providers-odbc==4.0.0
   apache-airflow-providers-openlineage==1.1.0
   apache-airflow-providers-postgres==5.6.1
   apache-airflow-providers-redis==3.3.2
   apache-airflow-providers-sendgrid==3.2.2
   apache-airflow-providers-sftp==4.6.1
   apache-airflow-providers-slack==8.1.0
   apache-airflow-providers-snowflake==5.0.1
   apache-airflow-providers-sqlite==3.4.3
   apache-airflow-providers-ssh==3.7.3
   ```
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Helm Chart 1.11.0
   Airflow 2.7.2
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to