Azure SFTPgo/AKS deployment fails

[djwheel105205]

Guys I have tried several times to deploy sftpgo and a new AKS cluster from the market place on Azure. The deployment fails with the following error:
{
"code": "UnmarshalError",
"message": "Invalid request body. Converting request body to a managed cluster encountered error: json: unknown field "storageProfile" Check that the field is in the right location, is spelled correctly, and is supported in the API version. Visit aka.ms/aks/apiversions for more API version information.."
}

The AKS version is 1.32.3, and in the template the storageProfile parameter is set to manageDisk

Any thoughts?

[drakkan]

Hello, are you using our official AKS offer? If so you don't need to ask support here on GitHub, contact us directly via email at support [at] sftpgo [dot] com and provide more info about what you did, we'll be glad to help. Thank you

[djwheel105205]

Yes, on official offer will follow up tomorrow.Thanks for your response!DwightSent from my iPhoneOn Apr 24, 2025, at 9:25 AM, Nicola Murino ***@***.***> wrote: Hello, are you using our official AKS offer? If so you don't need to ask support here on GitHub, contact us directly via email at support [at] sftpgo [dot] com and provide more info about what you did, we'll be glad to help. Thank you —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[drakkan]

Thanks for your feedback. The storageProfile field in our deployment template has been implemented in as in the official sample from Microsoft.

We’ve just updated our AKS offer and submitted it for validation, if there is some invalid field I expect the validation will fail.

Anyway we'll test a deployment of this version once the preview is created.

[djwheel105205]

Thanks Nicola! Not sure why this doesn't work... Anyway, will you let me know when I can try it again? Dwight

…

On Fri, Apr 25, 2025 at 3:32 AM Nicola Murino ***@***.***> wrote: Thanks for your feedback. The storageProfile field in our deployment template has been implemented in as in the official sample <https://github.com/Azure-Samples/kubernetes-offer-samples/blob/main/samples/k8s-offer-azure-vote/mainTemplate.json#L187> from Microsoft. We’ve just updated our AKS offer and submitted it for validation, if there is some invalid field I expect the validation will fail. Schermata.del.2025-04-25.10-31-02.png (view on web) <https://github.com/user-attachments/assets/66c062db-0628-466c-a588-b30cde7df76d> Anyway we'll test a deployment of this version once the preview is created. — Reply to this email directly, view it on GitHub <#1958 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFGHURN3DYXDU6LORNQ3Y6T23HXIBAVCNFSM6AAAAAB3ZEGEV2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJUGQ2DQNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[drakkan]

@djwheel105205 I’m able to reproduce the error. It’s evident that something has changed on the AKS side, as the offer worked in the past and we have active users. It's likely that validation has become more strict recently, as storageProfile is not defined in the schema and was probably just ignored in the past.

I have removed that field but unfortunately the process for testing AKS offerings is extremely time-consuming I have to submit the new version, wait for manual approval and only after this I can test if the offer really works. Each tests requires 3-4 hours at least. I have also opened a support tidket. I'll notify you once is fixed, sorry for the problem

[drakkan]

@djwheel105205 If you create the Kubernetes cluster first and then deploy the offer to that existing cluster, it works now. I've submitted another update that should also support creating a cluster and installing the offer in a single step. However, in a real-world scenario, you'd probably want to create the cluster separately using your preferred settings anyway.

[djwheel105205]

Okay, I will try that tomorrow. Sorry cooking dinner now. Dwight

…

On Fri, Apr 25, 2025 at 3:27 PM Nicola Murino ***@***.***> wrote: @djwheel105205 <https://github.com/djwheel105205> If you create the Kubernetes cluster first and then deploy the offer to that existing cluster, it works now. I've submitted another update that should also support creating a cluster and installing the offer in a single step. However, in a real-world scenario, you'd probably want to create the cluster separately using your preferred settings anyway. — Reply to this email directly, view it on GitHub <#1958 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFGHURNZSWQGCLT6NAPD3BL23KLEPAVCNFSM6AAAAAB3ZEGEV2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJVGEYDKMI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[drakkan]

The latest update also allow to deploy SFTPGo and create a new cluster using a single deployment.
Thanks for reporting this issue.