Aks-engine: Expose AzureCNIVersion in apimodel

[davidmatson]

Is this a request for help?:

No

Is this an ISSUE or FEATURE REQUEST? (choose one):

FEATURE REQUEST

AzureCNIVersion isn't included in the KubernetesConfig doc list. Based on a quick search through the source, I believe setting this property is the right way to get a different version of this plugin installed.

[davidmatson]

Actually, AzureCNIVersion doesn't seem to work. What's the right way to choose a custom version?

[zhiweiv]

https://github.com/Azure/azure-container-networking/issues/287 works for me.

[CecileRobertMichon]

Hi @davidmatson, the AzureCNIVersion is not currently user configurable in the apimodel.

[davidmatson]

Thanks. I'll try azureCNIURLWindows instead. If we could expose AzureCNIVersion (without the required "v" prefix for consistency), that would be great too.

[jsturtevant]

The version string is not configurable but I believe you can control both the Windows and Linux version via the following settings passing a full url to a Azure CNI Release:

orchestratorProfile.kubernetesConfig.azureCNIURLWindows=$WINDOWS_AZURE_CNI_URL
orchestratorProfile.kubernetesConfig.azureCNIURLLinux=$LINUX_AZURE_CNI_URL

Example url: https://github.com/Azure/azure-container-networking/releases/download/v1.0.16/azure-vnet-cni-linux-amd64-v1.0.16.tgz

[davidmatson]

Yes, I was able to use the full URL for now. Thanks.

[jackfrancis]

Removing the "help wanted" label because I think we want to use this particular request as an excuse to generalize "user-configurable k8s pre-reqs". Rather than simply bolt on Azure CNI version as a user-configurable feature in an existing flat structure (e.g., KubernetesConfig) we'd benefit in the long term by having this type of configuration be structured and implemented in a way that was distinct, and could accommodate independent maintenance (i.e., not have to deliver a change to the Azure CNI version with an entire cluster upgrade operation).

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[davidmatson]

/remove-lifecycle stale
/lifecycle frozen

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[davidmatson]

/lifecyle remove-stale

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[davidmatson]

/lifecycle remove-stale
/lifecycle frozen

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[davidmatson]

/lifecycle remove-stale

[marosset]

Bumping this issue.
@rjaini ran into an issue where AzureCNI version was changed but packages for the new version were not present in the Windows VHD which broke in a disconnected scenario.

[jackfrancis]

No plans to change this configuration. As it stands now, this is the exception to most api model properties, in that it is read-only.