Deployment failed

[CapKenR]

Using the Azure CLI above to create a Kubernetes cluster with network policy, I get the following error.

Deployment failed. Error occurred in request., ConnectionError: HTTPSConnectionPool(host='management.azure.com', port=443): Max retries exceeded with url: /subscriptions/c5b0b06c-d53b-40ac-b336-a26fffc4e68f/providers/Microsoft.ContainerService/locations/centralus/operations/eaa6085b-b399-41c1-b1ec-90cf65dd600b?api-version=2017-08-31 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fac146b0ac8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

If I describe the one node provisioned, I see the following condition.

Ready False Tue, 02 Apr 2019 11:28:18 -0500 Tue, 02 Apr 2019 10:46:42 -0500 KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 13ac2648-7dce-c83c-0b14-79d5b091b1af
• Version Independent ID: 6aa0b306-6926-87cc-9b59-496ac91dfba6
• Content: Secure pods with network policies in Azure Kubernetes Service (AKS)
• Content Source: articles/aks/use-network-policies.md
• Service: container-service
• GitHub Login: @iainfoulds
• Microsoft Alias: iainfou

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[CapKenR]

BTW, if you replace --network-policy calico with --network-policy azure, the cluster creation works. I haven't tried the network policy examples with azure instead of calico but am assuming they should still work.

[mimckitt]

Thanks @CapKenR I actually just finished running a few tests and am getting a failure as well

I tried the network policy azure as well as that does appear to work.

@iainfoulds @sauryadas Who is the best person to assign this to/ work with to get this sorted out? I see it is still in preview.

[ingeknudsen]

We have also faced the same issue when creating the cluster using calico as --network-policy. However we have also seen the same effect when scaling an existing cluster created using calico. All new nodes are left hanging in a NotReady state. The cluster is otherwise working well.

[axelgMS]

This is a new bug - it's currently being fixed. Will write back here when test & validation are ok

[mimckitt]

Thanks @axelgMS

[feiskyer]

Yep, this is bug for v1.12.x. versions below that are still working

[katrinsharp]

This is a new bug - it's currently being fixed. Will write back here when test & validation are ok

@axelgMS Is there a github issue I can follow? Thanks!

[katrinsharp]

Thanks, I'll check it out!

…

On Wed, Apr 10, 2019 at 9:57 AM Axel Guerrier ***@***.***> wrote: we had confirmation that the deployment on AKS 1.11.9 works fine — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#28567 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmj6Cz6h1F6HDwH2DfSIP_aD24Mgp0Eks5vfe3NgaJpZM4cYow5> .

-- Best Regards, Katrin

[mimckitt]

I will close this as it is being worked on and there are no changes needed from a doc perspective at this time.

[keaaa]

Why are issues closed that is in progress? How will we then know when this is fixed?

We also had a support ticket in azure for the same issue, which was closed - azure support said we should follow this issue for updates.

[mimckitt]

@axelgMS @feiskyer where can users follow this bug? Is there a GitHub link we can follow? I dont think it makes sense to keep an issue open on this specific doc as there is not an actual doc problem but a product issue.

[feiskyer]

@MicahMcKittrick-MSFT See Azure/AKS#905.

[keaaa]

thanks :)