You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/how-to-managed-cluster-networking.md
+67Lines changed: 67 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -353,6 +353,73 @@ The following steps describe enable public IP on your node.
353
353
az vmss list-instance-public-ips -g MC_MyResourceGroup2_MyManagedCluster_eastus -n YourVirtualMachineScaleSetName
354
354
```
355
355
356
+
The command outputs in JSON format.
357
+
358
+
```json
359
+
[
360
+
{
361
+
"etag": "etag_0",
362
+
"id": "<id_0/name>",
363
+
"idleTimeoutInMinutes": 15,
364
+
"ipAddress": "<ip_address_0>",
365
+
"ipConfiguration": {
366
+
"id": "<configuration_id_0>",
367
+
"resourceGroup": "<your_resource_group"
368
+
},
369
+
"ipTags": [],
370
+
"name": "<name>",
371
+
"provisioningState": "Succeeded",
372
+
"publicIPAddressVersion": "IPv4",
373
+
"publicIPAllocationMethod": "Static",
374
+
"resourceGroup": "<your_resource_group",
375
+
"resourceGuid": "resource_guid_0",
376
+
"sku": {
377
+
"name": "Standard"
378
+
}
379
+
},
380
+
{
381
+
"etag": "etag_1",
382
+
"id": "/<id_1/name>",
383
+
"idleTimeoutInMinutes": 15,
384
+
"ipAddress": "<ip_address_1>",
385
+
"ipConfiguration": {
386
+
"id": "<configuration_id_1>",
387
+
"resourceGroup": "<your_resource_group"
388
+
},
389
+
"ipTags": [],
390
+
"name": "<name>",
391
+
"provisioningState": "Succeeded",
392
+
"publicIPAddressVersion": "IPv4",
393
+
"publicIPAllocationMethod": "Static",
394
+
"resourceGroup": "<your_resource_group>",
395
+
"resourceGuid": "resource_guid_1",
396
+
"sku": {
397
+
"name": "Standard"
398
+
}
399
+
},
400
+
{
401
+
"etag": "etag_2",
402
+
"id": "<id_2/name>",
403
+
"idleTimeoutInMinutes": 15,
404
+
"ipAddress": "<ip_address_2>",
405
+
"ipConfiguration": {
406
+
"id": "<configuration_id_2>",
407
+
"resourceGroup": "<your_resource_group"
408
+
},
409
+
"ipTags": [],
410
+
"name": "<name>",
411
+
"provisioningState": "Succeeded",
412
+
"publicIPAddressVersion": "IPv4",
413
+
"publicIPAllocationMethod": "Static",
414
+
"resourceGroup": "<your_resource_group>",
415
+
"resourceGuid": "resource_guid_2",
416
+
"sku": {
417
+
"name": "Standard"
418
+
}
419
+
}
420
+
]
421
+
```
422
+
356
423
<a id="ipv6"></a>
357
424
## Enable IPv6
358
425
Managed clusters don't enable IPv6 by default. This feature will enable full dual stack IPv4/IPv6 capability from the Load Balancer frontend to the backend resources. Any changes you make to the managed cluster load balancer config or NSG rules will affect both the IPv4 and IPv6 routing.
0 commit comments