-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Azure Container Instance Operator uses deprecated "network profile" arg #34820
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
#34738 is now working on it. I think it will be included in the next azure provider release |
@pankajastro I assume this issue is fixed in #34738 ? |
I removed network_profile in #34738 but just created a separate PR #34850 to add subnet_ids |
Do we also need to add in a virtual network param? |
the subnet is something like and can't see specific param for vnet in SDK
|
closing as task is completed and it seems more like a support question. |
Apache Airflow version
2.7.1
What happened
The Azure Container Instance Operator uses the "network profile" argument which is since deprecated by Microsft: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-vnet
Azure Container Instances deployed by the Operator are not deployed into a virtual network or subnet.
What you think should happen instead
Get rid of the network profile argument and replace with "vnet" and "subnet" arguments as detailed in this documentation: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-vnet
How to reproduce
Deploy azure container instance - there are no longer network profiles supported by Azure. Will not let you deploy into your virtual network or subnet.
Operating System
linux
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: