-
Notifications
You must be signed in to change notification settings - Fork 295
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Vsphere failure domain API changes (#9223)
* Add vsphere failure domains api changes * Add vsphere failure domain manifests * Fix lint formatting * Move failure domain validation to types
- Loading branch information
1 parent
6e257cf
commit f0fc3fa
Showing
8 changed files
with
559 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
67 changes: 67 additions & 0 deletions
67
pkg/api/v1alpha1/testdata/vsphere_cluster_valid_failuredomains.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
apiVersion: anywhere.eks.amazonaws.com/v1alpha1 | ||
kind: Cluster | ||
metadata: | ||
name: eksa-unit-test | ||
spec: | ||
controlPlaneConfiguration: | ||
count: 3 | ||
endpoint: | ||
host: test-ip | ||
machineGroupRef: | ||
name: eksa-unit-test | ||
kind: VSphereMachineConfig | ||
kubernetesVersion: 1.20 | ||
workerNodeGroupConfigurations: | ||
- count: 3 | ||
machineGroupRef: | ||
name: eksa-unit-test | ||
kind: VSphereMachineConfig | ||
name: "md-0" | ||
datacenterRef: | ||
kind: VSphereDatacenterConfig | ||
name: eksa-unit-test | ||
clusterNetwork: | ||
cni: "cilium" | ||
pods: | ||
cidrBlocks: | ||
- 192.168.0.0/16 | ||
services: | ||
cidrBlocks: | ||
- 10.96.0.0/12 | ||
--- | ||
apiVersion: anywhere.eks.amazonaws.com/v1alpha1 | ||
kind: VSphereMachineConfig | ||
metadata: | ||
name: eksa-unit-test | ||
spec: | ||
diskGiB: 25 | ||
datastore: "myDatastore" | ||
folder: "myFolder" | ||
memoryMiB: 8192 | ||
numCPUs: 2 | ||
osFamily: "ubuntu" | ||
resourcePool: "myResourcePool" | ||
storagePolicyName: "myStoragePolicyName" | ||
template: "myTemplate" | ||
users: | ||
- name: "mySshUsername" | ||
sshAuthorizedKeys: | ||
- "mySshAuthorizedKey" | ||
--- | ||
apiVersion: anywhere.eks.amazonaws.com/v1alpha1 | ||
kind: VSphereDatacenterConfig | ||
metadata: | ||
name: eksa-unit-test | ||
spec: | ||
datacenter: "myDatacenter" | ||
network: "myNetwork" | ||
server: "myServer" | ||
thumbprint: "myTlsThumbprint" | ||
insecure: false | ||
failureDomains: | ||
- name: "fd-1" | ||
computeCluster: "myComputeCluster" | ||
resourcePool: "myResourcePool" | ||
datastore: "myDatastore" | ||
folder: "myFolder" | ||
network: "/myDatacenter/network/myNetwork" |
Oops, something went wrong.