From 550ee3a655b85d02ff911a5cd1d255deb77d6d49 Mon Sep 17 00:00:00 2001 From: bbharathan Date: Tue, 16 May 2023 18:15:01 +0530 Subject: [PATCH 1/4] avi_dns Signed-off-by: bbharathan --- src/deployment-guides/tkg-avi-dns.md | 64 ++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 src/deployment-guides/tkg-avi-dns.md diff --git a/src/deployment-guides/tkg-avi-dns.md b/src/deployment-guides/tkg-avi-dns.md new file mode 100644 index 00000000..ca65337c --- /dev/null +++ b/src/deployment-guides/tkg-avi-dns.md @@ -0,0 +1,64 @@ +# AVI DNS Virtual Service with TKGM + +The Purpose of thie Document is to demonstrate how we can leverage AVI DNS Virtual Service to as a DNS Server for workload application.For More information Please refer [**Product Documentation**](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-EF35646D-8762-41F1-95E5-D2F35ED71BA1.html) . + +AVI DNS Virtual Service is available only in AVI Enterprice license or more. + +## General Instructions for Installing AVI DNS and L7 Ingress Service Provider. + +NSX ALB as in L7 Ingress Service Provider + +We will be Deploying NSX ALB L7 ingress in NodePortLocal mode in our infrastructure, For more information please refer NSX ALB as in L4+L7 Ingress Service Provider Session in Referance Architecture. + + +Link will be given here to our RA + +L7 functionality will be enabled using AKO configuration files as part of the Management cluster deployment. + +Deployment file will given here for referance. +### Create a Service Engine Group. +To create or edit an SE group: + +1. Select Infrastructure > Clouds and click on the cloud name (for example, Default-Cloud). +2. Select Service Engine Group to open the Service Engine Groups page, which lists the SE groups currently configured in Vantage. +3. Click New Service Engine Group or click on an SE group name in the table. + +The create and edit popups for SE groups have identical properties. This popup includes the following tabs: + +* Upate the Service Engine Group Name. +* Select High Availability to Active/Active. +* VS Placement across Service Engines should be Compact. + +### Configuring DNS + +DNS Virtual Service +Starting with release 18.1.2, the DNS virtual service can be configured with IPv4 VIP, IPv6 VIP, or a dual VIP. + +Navigate to Applications > Virtual Services and click on Create Virtual Service (Advanced Setup) Select the Cloud. Configuration tabs associated with DNS are as explained below. + +Settings +* Update **Name** +* VS +* **TCP/UDP Profile** Select System-UDP-Per-Pkt. +* **Application Profiles** Select Select System-DNS. +* In **VS VIP** Select **Create VS VIP** Enter Name & under **VIP** Select **ADD** + + * **Private IP** > **Auto-Allocate** + * **IP Protocol** > **V4 Only** + * **VIP Address Allocation Network** > **sfo01-w01-vds01-tkgmanagementvip** + * **IPv4 Subnet** > Select the Defined network +* Click **SAVE** + +### Configuring DNS Name + +DNS Profile will be created as part of the Managment cluster creation. + +Navigate to **Templates** > **IPAM/DNS Profiles** and Select the DNS **Virtual Service** +by using the drop-down option. + +* Update the DNS Name for AVI DNS by Selecting **ADD** > **SAVE** + +### Update AVI DNS Service + +Navigate to **Administration** > **DNS Service** and Select the DNS profile **Click** on pencil icon to **EDIT**. + From d6a4371813a714b1d061c35aa3ce8f75da9392b3 Mon Sep 17 00:00:00 2001 From: bbharathan Date: Wed, 17 May 2023 09:40:43 +0530 Subject: [PATCH 2/4] avidns Signed-off-by: bbharathan --- src/deployment-guides/tkg-avi-dns.md | 37 ++++++++++++++++------------ 1 file changed, 21 insertions(+), 16 deletions(-) diff --git a/src/deployment-guides/tkg-avi-dns.md b/src/deployment-guides/tkg-avi-dns.md index ca65337c..c136c97c 100644 --- a/src/deployment-guides/tkg-avi-dns.md +++ b/src/deployment-guides/tkg-avi-dns.md @@ -2,11 +2,11 @@ The Purpose of thie Document is to demonstrate how we can leverage AVI DNS Virtual Service to as a DNS Server for workload application.For More information Please refer [**Product Documentation**](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-EF35646D-8762-41F1-95E5-D2F35ED71BA1.html) . -AVI DNS Virtual Service is available only in AVI Enterprice license or more. +AVI DNS Virtual Service is available only in **AVI Enterprice** license or more.For more information about AVI DNS Architecture please refer product [documentation](https://avinetworks.com/docs/latest/avi-dns-architecture/) ## General Instructions for Installing AVI DNS and L7 Ingress Service Provider. -NSX ALB as in L7 Ingress Service Provider +NSX ALB as in **L7 Ingress Service Provider** We will be Deploying NSX ALB L7 ingress in NodePortLocal mode in our infrastructure, For more information please refer NSX ALB as in L4+L7 Ingress Service Provider Session in Referance Architecture. @@ -19,33 +19,36 @@ Deployment file will given here for referance. ### Create a Service Engine Group. To create or edit an SE group: -1. Select Infrastructure > Clouds and click on the cloud name (for example, Default-Cloud). -2. Select Service Engine Group to open the Service Engine Groups page, which lists the SE groups currently configured in Vantage. -3. Click New Service Engine Group or click on an SE group name in the table. +1. Select Infrastructure > **Cloud Resources** and click on the cloud name (for example, sfow01vc01). +2. Click on **CREATE** -The create and edit popups for SE groups have identical properties. This popup includes the following tabs: + * Upate the Service Engine Group Name. + * Select High Availability to Active/Active. + * VS Placement across Service Engines should be Compact. +### Update IPAM Profile -* Upate the Service Engine Group Name. -* Select High Availability to Active/Active. -* VS Placement across Service Engines should be Compact. +We will be using **sfo01-w01-vds01-albmanagement** network for DNS virtual Service IP. -### Configuring DNS +Navigate to **Templates** > **IPAM/DNS Profiles** and Edit the IPAM Profile. + +Add the Network by selecting cloud under **Cloud** > **ADD** Select **sfo01-w01-vds01-albmanagement** > **SAVE** + +### Configuring DNS Virtual Service -DNS Virtual Service Starting with release 18.1.2, the DNS virtual service can be configured with IPv4 VIP, IPv6 VIP, or a dual VIP. -Navigate to Applications > Virtual Services and click on Create Virtual Service (Advanced Setup) Select the Cloud. Configuration tabs associated with DNS are as explained below. +Navigate to **Applications** > **Virtual Services** and click on **CREATE VIRTUAL SERVICE** (Advanced Setup) Select the Cloud Click **NEXT**. Configuration tabs associated with DNS are as explained below. Settings * Update **Name** * VS -* **TCP/UDP Profile** Select System-UDP-Per-Pkt. * **Application Profiles** Select Select System-DNS. -* In **VS VIP** Select **Create VS VIP** Enter Name & under **VIP** Select **ADD** - +* **TCP/UDP Profile** Select System-UDP-Per-Pkt. +* In **VS VIP** Select **Create VS VIP** Enter Name & under **General** Select **ADD** to add **VIP** + * **Enable VIP** * **Private IP** > **Auto-Allocate** * **IP Protocol** > **V4 Only** - * **VIP Address Allocation Network** > **sfo01-w01-vds01-tkgmanagementvip** + * **VIP Address Allocation Network** > **sfo01-w01-vds01-albmanagement** * **IPv4 Subnet** > Select the Defined network * Click **SAVE** @@ -62,3 +65,5 @@ by using the drop-down option. Navigate to **Administration** > **DNS Service** and Select the DNS profile **Click** on pencil icon to **EDIT**. + + From 2b0f8f916531d9ca9ff0e5a7086ebc97c0a67d81 Mon Sep 17 00:00:00 2001 From: bbharathan Date: Wed, 17 May 2023 09:52:35 +0530 Subject: [PATCH 3/4] avidns Signed-off-by: bbharathan --- src/deployment-guides/tkg-avi-dns.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/deployment-guides/tkg-avi-dns.md b/src/deployment-guides/tkg-avi-dns.md index c136c97c..291ed550 100644 --- a/src/deployment-guides/tkg-avi-dns.md +++ b/src/deployment-guides/tkg-avi-dns.md @@ -1,28 +1,28 @@ -# AVI DNS Virtual Service with TKGM +# AVI DNS Virtual Service with Tanzu Kubernetes Grid -The Purpose of thie Document is to demonstrate how we can leverage AVI DNS Virtual Service to as a DNS Server for workload application.For More information Please refer [**Product Documentation**](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-EF35646D-8762-41F1-95E5-D2F35ED71BA1.html) . +The Purpose of the Document is to demonstrate how we can leverage AVI DNS Virtual Service to as a DNS Server for workload application.For More information Please refer [**Product Documentation**](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-EF35646D-8762-41F1-95E5-D2F35ED71BA1.html) . -AVI DNS Virtual Service is available only in **AVI Enterprice** license or more.For more information about AVI DNS Architecture please refer product [documentation](https://avinetworks.com/docs/latest/avi-dns-architecture/) +AVI DNS Virtual Service is available only in **AVI Enterprise** license or more.For more information about AVI DNS Architecture please refer product [documentation](https://avinetworks.com/docs/latest/avi-dns-architecture/) ## General Instructions for Installing AVI DNS and L7 Ingress Service Provider. NSX ALB as in **L7 Ingress Service Provider** -We will be Deploying NSX ALB L7 ingress in NodePortLocal mode in our infrastructure, For more information please refer NSX ALB as in L4+L7 Ingress Service Provider Session in Referance Architecture. +We will be Deploying NSX ALB L7 ingress in NodePortLocal mode in our infrastructure, For more information please refer NSX ALB as in L4+L7 Ingress Service Provider Session in Reference Architecture. Link will be given here to our RA L7 functionality will be enabled using AKO configuration files as part of the Management cluster deployment. -Deployment file will given here for referance. +Deployment file will given here for reference. ### Create a Service Engine Group. To create or edit an SE group: 1. Select Infrastructure > **Cloud Resources** and click on the cloud name (for example, sfow01vc01). 2. Click on **CREATE** - * Upate the Service Engine Group Name. + * Update the Service Engine Group Name. * Select High Availability to Active/Active. * VS Placement across Service Engines should be Compact. ### Update IPAM Profile @@ -54,7 +54,7 @@ Settings ### Configuring DNS Name -DNS Profile will be created as part of the Managment cluster creation. +DNS Profile will be created as part of the Management cluster creation. Navigate to **Templates** > **IPAM/DNS Profiles** and Select the DNS **Virtual Service** by using the drop-down option. From 7b9d09f110c2e60f0f28fb77cfc73ae7f81115bf Mon Sep 17 00:00:00 2001 From: bbharathan Date: Thu, 18 May 2023 15:32:11 +0530 Subject: [PATCH 4/4] update_10 Signed-off-by: bbharathan --- src/deployment-guides/tkg-avi-dns.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/deployment-guides/tkg-avi-dns.md b/src/deployment-guides/tkg-avi-dns.md index 291ed550..d5cab877 100644 --- a/src/deployment-guides/tkg-avi-dns.md +++ b/src/deployment-guides/tkg-avi-dns.md @@ -63,7 +63,4 @@ by using the drop-down option. ### Update AVI DNS Service -Navigate to **Administration** > **DNS Service** and Select the DNS profile **Click** on pencil icon to **EDIT**. - - - +Navigate to **Administration** > **DNS Service** and Select the DNS profile **Click** on pencil icon to **EDIT**. \ No newline at end of file