Skip to content

Commit fb31f68

Browse files
authored
Update l4-load-balancing.md
have to use v1beta1 instead of v1alpha1
1 parent c2b8978 commit fb31f68

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/kubernetes-fleet/l4-load-balancing.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ In this how-to guide, you'll set up layer 4 load balancing across workloads depl
8585
1. Create the following `ClusterResourcePlacement` in a file called `crp-2.yaml`. Notice we're selecting clusters in the `eastus` region:
8686
8787
```yaml
88-
apiVersion: fleet.azure.com/v1alpha1
88+
apiVersion: placement.kubernetes-fleet.io/v1beta1
8989
kind: ClusterResourcePlacement
9090
metadata:
9191
name: kuard-demo
@@ -98,10 +98,11 @@ In this how-to guide, you'll set up layer 4 load balancing across workloads depl
9898
policy:
9999
affinity:
100100
clusterAffinity:
101-
clusterSelectorTerms:
101+
requiredDuringSchedulingIgnoredDuringExecution:
102+
clusterSelectorTerms:
102103
- labelSelector:
103104
matchLabels:
104-
fleet.azure.com/location: eastus
105+
fleet.azure.com/location: koreacentral
105106
```
106107
107108
1. Apply the `ClusterResourcePlacement`:
@@ -113,7 +114,7 @@ In this how-to guide, you'll set up layer 4 load balancing across workloads depl
113114
If successful, the output will look similar to the following example:
114115
115116
```console
116-
clusterresourceplacement.fleet.azure.com/kuard-demo created
117+
clusterresourceplacement.placement.kubernetes-fleet.io/kuard-demo created
117118
```
118119
119120
1. Check the status of the `ClusterResourcePlacement`:

0 commit comments

Comments
 (0)