Fixing Dapr + Flux race condition

[Gordonby]

PR Summary

This fixes a bug where if you configured Flux and Dapr, then they would conflict with each other whilst installing simultaneously.

It also addresses another small issue with the default parameter value for upgradeChannel

Closes #385
Closes #389

PR Checklist

• PR has a meaningful title
• Summarized changes
• This PR is ready to merge and is not Work in Progress
• Link to a filed issue

[khowling]

awesome fixes, good investigation!!

[joshuadmatthews]

I am having this issue even with the dependencies chained, I can see that flux is fully finished before dapr starts up yet, dapr is the only thing deploying while it is deploying, yet I still get the EtagMismatch error. Any ideas?

[Gordonby]

I am having this issue even with the dependencies chained, I can see that flux is fully finished before dapr starts up yet, dapr is the only thing deploying while it is deploying, I yet still get the EtagMismatch error. Any ideas?

Can you share the full error?
Just redact your subscription Id etc.

[joshuadmatthews]

{
    "status": "Failed",
    "error": {
        "code": "ExtensionOperationFailed",
        "message": "The extension operation failed with the following error:  Request failed to https://management.azure.com/subscriptions/xyz/resourceGroups/abc/providers/Microsoft.ContainerService/managedclusters/aks/extensionaddons/dapr?api-version=2021-03-01. Error code: Conflict. Reason: Conflict.{\n  \"code\": \"EtagMismatch\",\n  \"message\": \"Failed to save managed aks in subscription xyz, resource abc. Operation is not allowed: Another operation is in progress\",\n  \"subcode\": \"PutManagedClusterAndAgentPools_FailedPrecondition\"\n }."
    }
}

[joshuadmatthews]

I think it may be something else wrong with my cluster, even if I disable remove the flux addon I still get this error.

[joshuadmatthews]

Deleting my cluster and letting it recreate resolved the issue.