文件列表:

pks-logo.png (27502, 2023-02-11)
screenshot-vmware-pks-lab-deployment-0.png (341264, 2023-02-11)
screenshot-vmware-pks-lab-deployment-1.png (66201, 2023-02-11)
screenshot-vmware-pks-lab-deployment-2.png (127876, 2023-02-11)
vmware-pks-lab-deployment.ps1 (108796, 2023-02-11)

# VMware Pivotal Container Service (PKS) Automated Lab Deployment  ## Table of Contents * [Description](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/#description) * [Changelog](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/#changelog) * [Requirements](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/#requirements) * [Configuration](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/#configuration) * [Logging](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/#logging) * [Sample Execution](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/#sample-execution) ## Description Automated deployment of the infrastructure (Nested ESXi including VSAN storage, NSX-T & Pivotal Ops Manager) required for configuring Pivotal Container Service (PKS) using PowerCLI. You just need a vCenter Server 6.5 or greater endpoint along with a single physical ESXi host to deploy the infrastructure to. For information, you can refer to this blog post [here](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/http://www.virtuallyghetto.com/2018/06/vghetto-automated-pivotal-container-service-pks-lab-deployment.html) for more details. Below is an screenshot of an example deployment:  ## Changelog * 06/19/28 * Removed Windows-specific dependencies, can now run on MacOS & Linux using PowerShell Core * Automate to deployment and configuration all PKS components (Ops Manager, BOSH Director & Harbor) ## Requirements * vCenter Server endpoint running at least vSphere 6.5 or later * Windows system that supports PowerCLI * [PowerCLI 10.1](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://code.vmware.com/web/dp/tool/vmware-powercli/10.1.0) or greater * Download [vmware-pks-lab-deployment.ps1](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/vmware-pks-lab-deployment.ps1) script * Nested ESXi [6.5d](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://download3.vmware.com/software/vmw-tools/nested-esxi/Nested_ESXi6.5d_Appliance_Template_v1.0.ova) or [6.5 Update 1](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://download3.vmware.com/software/vmw-tools/nested-esxi/Nested_ESXi6.5u1_Appliance_Template_v1.0.ova) Virtual Appliance OVA * Enable either [MAC Learning](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://williamlam.com/2018/04/native-mac-learning-in-vsphere-6-7-removes-the-need-for-promiscuous-mode-for-nested-esxi.html) or [Promiscuous Mode](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://kb.vmware.com/kb/1004099) on your physical ESXi host networking to ensure proper network connectivity for Nested ESXi workloads * NSX-T 2.1 * [NSX-T 2.1 Manager for ESXi OVA](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://my.vmware.com/group/vmware/details?downloadGroup=NSX-T-210&productId=673&download=true&fileId=ceb09d4c2a044e745be0e5ab7f6***295&secureParam=4faa362cd30eda7241a9471ee692774b&uuId=e268e430-59fd-45f2-a7c4-08629fe084ef&downloadType=) * [NSX-T 2.1 Controller for ESXi OVA](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://my.vmware.com/group/vmware/details?downloadGroup=NSX-T-210&productId=673&download=true&fileId=46f4cf5fa854bcd4f2c74f849e7acb69&secureParam=852f862526f99ea5f73fda3fb455ca14&uuId=e7c7f09a-3567-4aa4-9c80-d30bdae030fe&downloadType=) * [NSX-T 2.1 Edge For ESXi OVA](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://my.vmware.com/group/vmware/details?downloadGroup=NSX-T-210&productId=673&download=true&fileId=46bdb3be8b48cdea045eed660a9d68d0&secureParam=35cf3c9f5f143fd48a74afd1773cde7f&uuId=dd993136-275e-43b6-83e7-6ba10fec89ac&downloadType=) * [Ops Manager CLI (OM)](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://github.com/pivotal-cf/om/releases) * Windows - om-windows.exe * MacOS - om-darn * Linux - om-linux * [Pivotal Ops Manager 2.1.5 OVA](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://network.pivotal.io/products/ops-manager) * [Pivotal Container Service 1.0.4 Tile](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://network.pivotal.io/products/pivotal-container-service) * [Harbor 1.4.2 Tile](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://network.pivotal.io/products/harbor-container-registry) * [Stemcell 3468.42](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://network.pivotal.io/products/stemcells#/releases/97389) ## Configuration This section describes the credentials to your vCenter Server in which the PKS lab environment will be deployed to: ```console $VIServer = "vcenter.primp-industries.com" $VIUsername = "primp" $VIPassword = "-->MySuperDuperSecurePassword<--" ``` This section describes the location of the OVA files that are required for deployment. If you are using MacOS or Linux, simply update the path to reflect those systems ```console $NestedESXiApplianceOVA = "C:\Users\primp\Desktop\Nested_ESXi6.5u1_Appliance_Template_v1.0.ova" $NSXTManagerOVA = "C:\Users\primp\Desktop\nsx-unified-appliance-2.1.0.0.0.7395503.ova" $NSXTControllerOVA = "C:\Users\primp\Desktop\nsx-controller-2.1.0.0.0.7395493.ova" $NSXTEdgeOVA = "C:\Users\primp\Desktop\nsx-edge-2.1.0.0.0.7395502.ova" $PKSOpsMgrOVA = "C:\Users\primp\Desktop\pcf-vsphere-2.1-build.318.ova" ``` This section describes the location fo the PKS specific binaries that must also be downloaded locally to your system. If you are using MacOS or Linux, simply update the path to reflect those systems. In addition, make sure that your OM CLI is for your specific platform or you will have issues :) ```console $OMCLI = "C:\Users\primp\Desktop\om-windows.exe" $PKSTile = "C:\Users\primp\Desktop\pivotal-container-service-1.0.4-build.5.pivotal" $HarborTile = "C:\Users\primp\Desktop\harbor-container-registry-1.4.2-build.14.pivotal" $Stemcell = "C:\Users\primp\Desktop\bosh-stemcell-3468.42-vsphere-esxi-ubuntu-trusty-go_agent.tgz" ``` This section describes the Ops Manager deployment configuration ```console $OpsManagerDisplayName = "pks-opsmgr" $OpsManagerHostname = "pks-opsmgr.primp-industries.com" $OpsManagerIPAddress = "172.30.51.19" $OpsManagerNetmask = "255.255.255.0" $OpsManagerGateway = "172.30.51.1" $OpsManagerAdminPassword = "VMware1!" ``` This section defines the number of Nested ESXi VMs to deploy along with their associated IP Address(s). The names are merely the display name of the VMs when deployed. At a minimum, you should deploy at least three hosts, but you can always add additional hosts and the script will automatically take care of provisioning them correctly. ```console $NestedESXiHostnameToIPs = @{ "esxi-01" = "172.30.51.10" "esxi-02" = "172.30.51.11" "esxi-03" = "172.30.51.12" } ``` This section describes the resources allocated to each of the Nested ESXi VM(s). Depending on the deployment type, you may need to increase the resources. For Memory and Disk configuration, the unit is in GB. ```console $NestedESXivCPU = "2" $NestedESXivMEM = "24" #GB $NestedESXiCachingvDisk = "4" #GB $NestedESXiCapacityvDisk = "60" #GB ``` This section describes the location as well as the generic networking settings applied to the Nested ESXi, NSX-T & Ops Manager VMs. ```console $VirtualSwitchType = "VDS" # VSS or VDS $VMNetwork = "dv-vlan3251" $VMDatastore = "himalaya-local-SATA-dc3500-3" $VMNetmask = "255.255.255.0" $VMGateway = "172.30.51.1" $VMDNS = "172.30.0.100" $VMNTP = "pool.ntp.org" $VMPassword = "VMware1!" $VMDomain = "primp-industries.com" $VMSyslog = "172.30.51.170" # Applicable to Nested ESXi only $VMSSH = "true" $VMVMFS = "false" # Applicable to VC Deployment Target only $RootDatacenterName = "Production" $VMCluster = "Primp-Cluster" ``` This section describes the new vSphere Cluster which will be created for PKS Compute Cluster ```console $NewVCVSANClusterName = "PKS-Cluster" ``` This section describes the Ops Manager application configuration ```console $OpsmanAdminUsername = "admin" $OpsmanAdminPassword = "VMware1!" $OpsmanDecryptionPassword = "VMware1!" ``` This section describes the BOSH Director application configuration You can refer to this [blog post](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://www.virtuallyghetto.com/2018/03/getting-started-with-vmware-pivotal-container-service-pks-part-4-ops-manager-bosh.html) for more details on the individual settings ```console $BOSHvCenterUsername = "pks" $BOSHvCenterPassword = "VMware1!" $BOSHvCenterDatacenter = "Production" $BOSHvCenterPersistentDatastores = "himalaya-local-SATA-re4gp4T:storage,vsanDatastore" $BOSHvCenterEpemeralDatastores = "himalaya-local-SATA-re4gp4T:storage,vsanDatastore" $BOSHvCenterVMFolder = "PKS-VMS" $BOSHvCenterTemplateFolder = "PKS-TEMPLATES" $BOSHvCenterDiskFolder = "PKS-DISKS" # AZ Defintions $BOSHManagementAZ = @{ "AZ-Management" = "Primp-Cluster" } $BOSHComputeAZ = @{ "AZ-Compute" = "PKS-Cluster" } # Network Definitions $BOSHManagementNetwork = @{ "pks-mgmt-network" = @{ portgroupname = "dv-vlan3251" #represents the vSphere Portgroup or NSX-T Logical Switch Name cidr = "172.30.51.0/24" reserved_range = "172.30.51.1-172.30.51.30" dns = "172.30.0.100" gateway = "172.30.51.1" az = "AZ-Management" } } $BOSHServiceNetwork = @{ "k8s-mgmt-cluster-network" = @{ portgroupname = "K8S-Mgmt-Cluster-LS" #represents the vSphere Portgroup or NSX-T Logical Switch Name cidr = "10.10.0.0/24" reserved_range = "10.10.0.1" dns = "172.30.0.100" gateway = "10.10.0.1" az = "AZ-Compute" } } $BOSHManagementNetworkAssignment = "pks-mgmt-network" $BOSHManagementAZAssignment = "AZ-Management" ``` This section describes the PKS Control Plane application configuration You can refer to this [blog post](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://www.virtuallyghetto.com/2018/04/getting-started-with-vmware-pivotal-container-service-pks-part-5-pks-control-plane.html) for more details on the individual settings ```console $PKSDatacenter = $RootDatacenterName $PKSDatastore = "vsanDatastore" $PKSCluster = $NewVCVSANClusterName $PKSvCenter = $VIServer $PKSCPIMasterUsername = $BOSHvCenterUsername $PKSCPIMasterPassword = $BOSHvCenterPassword $PKSCPIWorkerUsername = $BOSHvCenterUsername $PKSCPIWorkerPassword = $BOSHvCenterPassword $PKSNSX = "nsx-mgr.primp-industries.com" $PKSNSXUsername = "admin" $PKSNSXPassword = "VMware1!" $PKSManagementNetworkAssignment = $BOSHManagementNetworkAssignment $PKSManagementAZAssignment = $BOSHManagementAZAssignment $PKSServiceNetworkAssignment = "k8s-mgmt-cluster-network" $PKSServiceAZAssignment = "AZ-Compute" $PKSPlan1AZ = "AZ-Compute" $PKSPlan2AZ = "AZ-Compute" $PKSUAAURL = "uaa.primp-industries.com" # The SSL Certificates are generated by the customer but you can use the following snippets to generate # the certs using openssl. Be sure to specify wildcard for your domain, this is whats asked of in PKS UIs # Copy the *.key and *.pem to the respective fields # openssl req -subj '/C=US/ST=CA/L=Santa Barbara/O=Primp-Industries/OU=R&D/CN=*.primp-industries.com' -out pks.csr -newkey rsa:2048 -nodes -keyout pks.key # openssl req -subj '/C=US/ST=CA/L=Santa Barbara/O=Primp-Industries/OU=R&D/CN=*.primp-industries.com' -x509 -sha256 -nodes -newkey rsa:2048 -keyout pks.key -out pks.pem # openssl req -subj '/C=US/ST=CA/L=Santa Barbara/O=Primp-Industries/OU=R&D/CN=*.primp-industries.com' -x509 -sha256 -nodes -days 730 -newkey rsa:2048 -keyout pks.key -out pks.pem $pksCertPEM = @' -----BEGIN CERTIFICATE----- MIIDyzCCArOgAwIBAgIJAOkdUNyqSIk+MA0GCSqGSIb3DQEBCwUAMHwxCzAJBgNV BAYTAlVTMQswCQYDVQQIDAJDQTEWMBQGA1UEBwwNU2FudGEgQmFyYmFyYTEZMBcG A1UECgwQUHJpbXAtSW5kdXN0cmllczEMMAoGA1UECwwDUiZEMR8wHQYDVQQDDBYq LnByaW1wLWluZHVzdHJpZXMuY29tMB4XDTE4MDYxNzAyMjM0M1oXDTIwMDYxNjAy MjM0M1owfDELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMRYwFAYDVQQHDA1TYW50 YSBCYXJiYXJhMRkwFwYDVQQKDBBQcmltcC1JbmR1c3RyaWVzMQwwCgYDVQQLDANS JkQxHzAdBgNVBAMMFioucHJpbXAtaW5kdXN0cmllcy5jb20wggEiMA0GCSqGSIb3 DQEBAQUAA4IBDwAwggEKAoIBAQDFHe3d1DfNmkAmLLmWnCXwjHa58FiPwHt30bje KsJ1Bbn4qx51Y8Rjp7jQ9zipFF8EaWfK0weym1PHyr2Pxq0EshYvWKl+in5rKshY qtLvsu3wZe5QpFQrbNgqsjpZ6/Vo1mjSgxYtZs1NyPNIv/ertM9iaTyileenUtnk XgUzRgUXYgzRzNsCd9zaKc6I11N2g8/EKa0WXN1x+908BLAvyAlDX5Hqa66tDjZE pIkRwRvmPWnoGj/wssfbw4wosfHaaCKvtv0AiAruheFy8Tmah19Zy6Jfuhc1sjzl YO3GXFHpePls5U+oYjurL/2VAdY7Y4ZR9dDnpIs7vQm1HqdjAgMBAAGjUDBOMB0G A1UdDgQWBBQXb8OC3C0S7ScHz76AtJQlv13HmjAfBgNVHSMEGDAWgBQXb8OC3C0S 7ScHz76AtJQlv13HmjAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQCy eiypyNOeW6l1wEiIyXZJT8TqZKqLzPlIUWWci/mcJwzmvi3S1pXxI0Ke2o***sikX hb3JEfLfUogXTLcRo2taUv2iDtvrRGhoJte8a2S51VxuPRFuhDWmaYUTwNHDf8uP 3S8WlkD8Foc2K6kK1UnfHN2CI43KC2Boce3jtyOz5Y4zABVMHoP0l4LxBUFnbhWu iV/ib/mMEoU4X3pX+JAjkVFSC2v0s9qhf4ws1shXgibx487hgZn8PqoQwXkPsaF/ n5U2jUtSM6d3Hxd2Jo1U+C6qfUSWBboI44w8rnyzI4u4hjwBE3S4NNh46+jkpv24 iC9imeTm7r/IXWZBfs87 -----END CERTIFICATE----- '@ $pksCertPrivateKey = @' -----BEGIN PRIVATE KEY----- MIIEvwIBADANBgkqhkiG9w0BAQEFAASCBKkwggSlAgEAAoIBAQDFHe3d1DfNmkAm LLmWnCXwjHa58FiPwHt30bjeKsJ1Bbn4qx51Y8Rjp7jQ9zipFF8EaWfK0weym1PH yr2Pxq0EshYvWKl+in5rKshYqtLvsu3wZe5QpFQrbNgqsjpZ6/Vo1mjSgxYtZs1N yPNIv/ertM9iaTyileenUtnkXgUzRgUXYgzRzNsCd9zaKc6I11N2g8/EKa0WXN1x +908BLAvyAlDX5Hqa66tDjZEpIkRwRvmPWnoGj/wssfbw4wosfHaaCKvtv0AiAru heFy8Tmah19Zy6Jfuhc1sjzlYO3GXFHpePls5U+oYjurL/2VAdY7Y4ZR9dDnpIs7 vQm1HqdjAgMBAAECggEBAK0acHbbVDohmO4tXrnt3L+XivgVIqDzJzp9GX05TdXY to2zMKdkeuYNN5eDU+Xf9uV372dF1b+6+mM9HyVxEyZJgoQHt6lh1E0moBSFx4Iq vxvbV+LHvQb5qggsxmOLfNOZXypnZgVu/yKtM0ETHFxVB75jrpUVUf82GhWbn7N6 4PvyFLi13FCu9LOP1hTkp5zHbMPm7K+Bmiyc5VHZVoPQp4Nsg6nspJkA7jXHZRLk QPNl581L80duAzKcKi3rptZsoPiYpsnWK7sp3HkoT6Dzn0PTupmJ3LUS2VEDliG+ qeKaEnGEWv/sxini01GDpqowo7H95MW2dGDaFwDn8BkCgYEA9dmXh0nyIX7F1nps EnPvkO85UpEbGRkXhcpSxyfW5YPIKsFRIxi9LAUpFgtBoWCbUYwXt54G6MlgQihw iZqx2sn8gKFz/CPJ5CaOmi36Eo0h6AfiUycMOsa/M/Cd4g47GOl0lETtg3JoiRue BP6wFgiKDAYNJZuQxLNilK0C/gcCgYEAzUFGDhQeC9CR/Pfs12Tfu7m21BB+Ci1c tsjwz84J6XKJ3D06DOEiB2tIgPiXz6PVRIUhL2mr25***gB6tSf2JW9Xht/8/KJTX ABccwUnz43wjkSFQ8XfZQD1UIDTwa4Cq6zuznQxJ2nznxpwb/5Gzzsn9QQwIKr/l Kw7H7MYadMUCgYEAncmvlScCfjjtJMChyB4crbq74aA78hnGnRnDkwqgw+GWgMpe FtZz42LUgc9rqfVk+iudtT15VcKZQxzNTaO5bqCgrLXyyOr3UrTkZVQI4gsurcsR mSjAkqCoat+NlV5o045SQi8S+YBeU1EkVDRaM2n7n8fqfC6h9XzkUmPQPdUCgYAn n+5SUXfrd/x3BbXnb0XyC8xL7FMoy9EWSHyU4YXwV3hd2EQYsG3NWNzKaTOFlm9Z pwndCV1wLJgZw9JYcmXOIOBOkSw0PWe0UMHwXsKCrDiBkBj8RNLgH/bZsN6pIlHc z83BB9pKH8rvALw2/n3j8gK+SABboGgxg8z83NHGsQKBgQDiPKp4weX0cP1/ablO MeMFIms+ISxjFi+f7iuXNs2LahbP/gK0fHyqM22ZLNsK3sb8KLc3PhykNZCpvE/s mlahgq***CyVapmK97GDLFEdbUXY1JY8XakcrDDUA8/GBM5IL0Vi6uLIeW8+pTa0L gr6moJLrg6EMbw1C7xWrzhxR0g== -----END PRIVATE KEY----- '@ ``` This section describes the Harbor application configuration You can refer to this [blog post](https://github.com/lamw/vmware-pks-automated-lab-deployment/blob/master/https://www.virtuallyghetto.com/2018/04/getting-started-with-vmware-pivotal-container-service-pks-part-7-harbor.html) for more details on the individual settings ```console $HarborAdminPassword = "VMware1!" $HarborHostname = "pks-harbor.primp-industries.com" $HarborManagementNetworkAssignment = $BOSHManagementNetworkAssignment $HarborManagementAZAssignment = $BOSHManagementAZAssignment # The SSL Certificates are generated by the customer but you can use the following snippets to generate # the certs using openssl. Be sure to specify wildcard for your domain, this is whats asked of in PKS UIs # Copy the *.key and *.pem to the respective fields #openssl req -subj '/C=US/ST=CA/L=Santa Barbara/O=Primp-Industries/OU=R&D/CN=*.primp-industries.com' -out harbor.csr -newkey rsa:2048 -nodes -keyout harbor.key #openssl req -subj '/C=US/ST=CA/L=Santa Barbara/O=Primp-Industries/OU=R&D/CN=*.primp-industries.com' -x509 -sha256 -nodes -newkey rsa:2048 -keyout harbor.key -out harbor.pem #openssl req -subj '/C=US/ST=CA/L=Santa Barbara/O=Primp-Industries/OU=R&D/CN=*.primp-industries.com' -x509 -sha256 -nodes -days 730 -newkey rsa:2048 -keyout harbor.key -out harbor.pem $harborCertPEM = @' -----BEGIN CERTIFICATE----- MIIDyzCCArOgAwIBAgIJANKigLa4gSLgMA0GCSqGSIb3DQEBCwUAMHwxCzAJBgNV BAYTAlVTMQswCQYDVQQIDAJDQTEWMBQGA1UEBwwNU2FudGEgQmFyYmFyYTEZMBcG A1UECgwQUHJpbXAtSW5kdXN0cmllczEMMAoGA1UECwwDUiZEMR8wHQYDVQQDDBYq LnByaW1wLWluZHVzdHJpZXMuY29tMB4XDTE4MDYxNzAyMjIwN1oXDTIwMDYxNjAy MjIwN1owfDELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMRYwFAYDVQQHDA1TYW50 YSBCYXJiYXJhMRkwFwYDVQQKDBBQcmltcC1JbmR1c3RyaWVzMQwwCgYDVQQLDANS JkQxHzAdBgNVBAMMFioucHJpbXAtaW5kdXN0cmllcy5jb20wggEiMA0GCSqGSIb3 DQEBAQUAA4IBDwAwggEKAoIBAQCzwhsWPQOb6wTX+wlfkhtllNHAoz6pswJbhezO JDvxw1L2sECUvvb0SFIPcKQnyIyaaS5IFlG03unFC/IbIKRVduTloc5gLEErfPy3 QKLlbEMzA/44K1vhqubY0568rbqJ4oVRSe/o7aaSaM68F7Nw5M+M9G5Yv6Ib9PAM CyLrFt8sg0u0uGvcNe4oz4ZrvZVcXf6XTH6RlQZsGZjBs6OMX5Svn2DimtcpLEsv Thzq6J3IeFNO5cbkksn0l7YVC6KW/wYxEHAN847Pf0dVnrQej2W7+W804RH0McJa Tupuzz0MDdZLMoe95UcvwXwkYrPg5smL0+dtckTKbH4bpUDfAgMBAAGjUDBOMB0G A1UdDgQWBBQjsCzrbQDpXmeFHVMDCnuq5GCbSzAfBgNVHSMEGDAWgBQjsCzrbQDp XmeFHVMDCnuq5GCbSzAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQAC kXYq0EPs7GYZznwscEcwi8DMb8gr5xsIZ7fU1akwaDPwT9a3mCyGeOEsnmf/wW55 LfQqXP1c3X9auTZ/N1GpP2qW/+PQA1hn825OcdLi6d+PFLPFS/Je+vr90GfTeZEG X0cljtAlHDEYTrh0m3Bp5QpxRto3Z7cTLermsIldBKuvc2SEuja4BYTLhot+urkN XvcJsPFO57D4f21qVVHXelVBEFbzn2Q+mWAb+emNi7tM45IMxWOh8pUl18888wKG dvLltkwohryDBtBICQB8JpZmdgLfSarCIQp13H0koMyR40DbZyachT8ftlcXIxAQ s3zI5HH8qWO16K17hjyz -----END CERTIFICATE----- '@ $harborCertPrivateKey = @' -----BEGIN PRIVATE KEY----- MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQCzwhsWPQOb6wTX +wlfkhtllNHAoz6pswJbhezOJDvxw1L2sECUvvb0SFIPcKQnyIyaaS5IFlG03unF C/IbIKRVduTloc5gLEErfPy3QKLlbEMzA/44K1vhqubY0568rbqJ4oVRSe/o7aaS aM68F7Nw5M+M9G5Yv6Ib9PAMCyLrFt8sg0u0uGvcNe4oz4ZrvZVcXf6XTH6RlQZs GZjBs6OMX5Svn2DimtcpLEsvThzq6J3IeFNO5cbkksn0l7YVC6KW/wYxEHAN847P f0dVnrQej2W7+W804RH0McJaTupuzz0MDdZLMoe95UcvwXwkYrPg5smL0+dtckTK bH4bpUDfAgMBAAECggEAV6Uis9sX8WPLvssFrPV+Ki8/fh+aI//F/H32EiSUnbJQ tzsEogHiQwUoDaMsRsF/3KHAESHgwMGXVZ4Xc6acuZb40AXuq/Gn7N5KEceQJTB+ K1edEiIB8Kv1Vm8IDJLgSu6JdjMIqJeHCgfUFN2xfi/yCpX7X4ZAMkVg7V5Yript d3qWGXPHDZg0LOc5CkaZhYO0pRCVTZfi7pM8Dxo+C8Mw/hLBwrEziL2kgyFMvUoU F5dTtMoy+yqyX2mEzg7YfA7kv70OhpyRQNZ+B1guXhgd+WDaanqxh7bRrRIG5RHd h3q/nyLrXdrSWLoHgM8KkYE/TYisW6fBsTGYSl1M8QKBgQDawUKVBbxEbqvjGPxC jQj3r5gHM0r1fdIASnyji2+c8zwZykN6s1E5pC6Tqz7GRwE6dlo6X4O3udGvlr8D RSb0IfzYRcZ2+Xyu/WPahzcRt+NL5Y70wmduH9xN2LaOGAupmRYyOLS5+8hWcf+O HuPRCLU7ICibjKkIfrSkLTU6WwKBgQDSXR67bRE0SIxJzJTW/1jq7+JLN4xbJ11O NxlCbJ0KYS0esHPzeOPBTKUJDQa8MIP0OD651mNLe5fU02RvAYkSzVUbrgjSOguu aRQD8+3YegIYk2amhA8/N7CZWBT0wdsXzfnX4CijJZUgp1q1IgtZWLMk5xQm6Ql6 IxbncGtyzQKBgQDD5oJ79hDtr7aav0tZRfgb59Jb0GF2i2C/BfWseDhR87mE1w+r GF7LIe7cK2UiJ4BAHLEcyWCp7eyMNJGGmi0SQEWwYHwlG7O++gisMJ7ubSFOXJuz MU1y33Fo/YQup/X5wbCQ9RtT2tlEIP7dBWi7T/MMqfXzpvnRM7cNt7aNNQKBgBwI 6PWVfXt4R6n2J8fXU+RLf***CUiQ7xMWNtkIR84PUm4zBe1JxQ/kY282u/LzLwmoj rMhbd/QxTnTAj1vz2m61CqibsvVBYxklS9OTCJmW+PyJeF6srtN/+nsVMAXGaApu GuPYLdJASfWGGCKXnOeVWJqMaTUeTXMHhh/l7YvpAoGAaobtDUTH78O27lVZ1IQ0 /LsT9S72DhcK3n5a40WUMXgdxoQwa+3YaURspr20eJzt4xenY+4dKaJ+VHPPOfiK 4UeazY1fbefUkA+ElzV8uaQEc0OVak8fbP9+5b05tiNgBpPP3Vo81Nb55FmbLJJe Z/bFvEcEbEabMJwxMyPl5ys= -----END PRIVATE KEY----- '@ ``` This section describes the general NSX-T configurations and most of the defaults can be left alone outside of the environmental specific configurations such as **NSXPrivatePortgroup** and **$NSXIntermediateNetworkPortgroup** property. You will also need an additional VLAN-backed portgroup (e.g. dv-vlan3250) to act as an intermediate network to bridge you management traffic to the NSX-T Logical Networks. This is only required if you are using static routes which I am using in my environment. If you are using BGP, this is not required but will require some modification to the NSX-T configuration post-deployment. ```console $NSXRootPassword = "VMware1!" $NSXAdminUsername = "admin" $NSXAdminPassword = "VMware1!" $NSXAuditUsername = "audit" $NSXAuditPassword = "VMware1!" $NSXSSHEnable = "true" $NSXEnableRootLogin = "true" $NSXPrivatePortgroup = "dv-private" $NSXIntermediateNetworkPortgroup = "dv-vlan3250" ``` This section describes the two IP Pools: Tunnel Endpoint for ESXi host and Load Balancer Pool for K8s ```console $TunnelEndpointPoolName = "ESXi-VTEP-Pool" $TunnelEndpointPoolDescription = "Tunnel Endpoint for ESXi Transport Nodes" $TunnelEndpointPoolIPRangeStart = "192.168.1.10" $TunnelEndpointPoolIPRangeEnd = "192.168.1.30" $TunnelEndpointPoolCIDR = "192.168.1.0/24" $TunnelEndpointPoolGateway = "192.168.1.1" $LoadBalancerPoolName = "Load-Balancer-Pool" $LoadBalancerPoolDescription = "Load Balancer IP Pool" $LoadBalancerPoolIPRangeStart = "10.20.0.10" $LoadBalancerPoolIPRangeEnd = "10.20.0.50" $LoadBalancerPoolCIDR = "10.20.0.0/24" ``` This section describes the IP Block used for K8s workload ```console $ipBlockName = "PKS-IP-Block" $ipBlockNetwork = "172.16.0.0/16" ``` This section describes the Transport Zones that will be created ```conso ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：