Open helbling-gum opened 8 months ago
:wave: @helbling-gum Thanks for filing this bug report.
A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.
For more information on our triage process please visit our triage overview
:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Steps to reproduce
Create a "Applications.Core/containers@2023-10-01-preview" ressource with the following extension:
Observed behavior
If a deployment is created with the extension mentioned above, the pod remains in the initialisation state. However, this only happens with the first radius deployment. If a deployment was previously created without this extension and this extension is added afterwards, the pods start without any problems.
Desired behavior
The deployment should also work if the extension is configured from the beginning and not only at the second deployment.
Workaround
Create deployment without extension. Execute Radius deployment. Add extension. Execute Radius deployment again.
rad Version
RELEASE VERSION BICEP COMMIT 0.26.6 v0.26.6 0.11.90 5e02b8a1706e7697d031db84a176f7c3f2053ee2
Operating system
Windows 11, x64
Tested Kubernets provider: AKS, EKS
Additional context
No response
Would you like to support us?
AB#11118