-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Support for init container in azurerm_container_group #8085
Comments
Hi @ArcturusZhang, |
Inspecting the current interface, I suppose we will have some problems with Volumes when introducing Init Containers, giving that both Containers and Init Containers should have the ability to share volumes. That's the current
It merges the concepts of both I would propose deprecating This is a proposal for volume_mount {
volume_name = ""
mount_path = ""
read_only = false
} Where This is a proposal for volume {
name = ""
azure_file {
share_name = ""
storage_account_name = ""
storage_account_key = ""
}
empty_dir = false
secret = {
"a" : "b"
}
git_repo {
url = ""
directory = ""
revision = ""
}
}
While being deprecated, we can still support After these changes, I believe we shouldn't have problems introducing volumes to Init Container using the same abstractions. This aligns with ARM template structure: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-volume-azure-files#mount-multiple-volumes Thoughts? |
Hey @allantargino appreciate if you could start - I only have a very simple start and then occupied by something else. |
Hi @ArcturusZhang / @allantargino , Any update on this issue? This can really help with the ACI usage. Thanks in advance. |
Hi @bdhar1, I ended up not implementing on this feature. |
Sharing volumes between containers is now supported using emptyDir, since #13374 |
Co-authored-by: zjhe <hezijie@microsoft.com> An enhancement as #8085 described.
Hello @johnksv and everyone, the |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
The provider should support init containers in Container Instances, as available through the CLI and as described here:
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-init-container
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: