Landscape Demo

[Rick Moore]

I tried to setup on AWS and being new to Kube, was not sure about the DNS m= odifications I need to make. I own a domain in AWS via route 53. If I call = the cluster "test" in domain "idgovaas.com". Do I need to generates records=  in DNS before running the setup?

 

Very excited to see SAP in this space.

 

Thanks

Rick

[Dominic Kistner]

Hi Rick,

 

The records are generated by the Kubify/Gardener setup – there is no need to do that manually. You need to make sure that the credentials for the hosted zone are specified correctly especially if the hosted zone is maintained in a different account. 

 

Cheers,

Dominic

[vasu 1124]

as Dominic mentioned, you can setup the Gardener in such a way that it created DNS entries for you.

More specific, when using the Dashboard you get a cluster YAML generated for you, which e.g looks like this:

 ...

  dns:
    provider: aws-route53
    hostedZoneID: Z1ZABCDEFG
    domain: <mycluster>.<myproject>.<subdomain.idgovaas.com>

...

In addition, a wildcard *.ingress.<your cluster domain> is generated and connected to the internal nginx ingress LB (currently only nginx, we are looking at istio based options).

If not using the Dashboard, you can of course modify your desired domain name and specify your own YAML.

Keep in mind: when dynamically creating clusters like sliced bread, the DNS entries for your clusters are time sensitive in the process. We have support for using DNS services from Azure & GCP, but we have had the best experiences with AWS Route 53.

Thanks for the thumbs-up!

BR Vasu

[Rick Moore]

Thanks, aside from my access & secret key. Does my modified yml file look correct? Will be nice having a reference example to learn with. I have been getting a headache trying to comprehend all that's really happening here :). More then happy to test on Azure once a happy path is provided. That's where all of my production lives right now.

Cheers

Rick