airshipit / treasuremap

Reference Airship manifests, CICD, and reference architecture.
http://openstack.org
Apache License 2.0
52 stars 39 forks source link

CI: DNS for ingress #40

Open drewwalters96 opened 4 years ago

drewwalters96 commented 4 years ago

Much like the seaworthy-virt framework in Airship 1, we need DNS configured in the continuous-integration pipelines to stimulate accessing dashboards from outside the cluster. Ideally, this would be a role that could be used by airshipit/treasuremap as well.

jezogwza commented 3 years ago

Lets move this issue to Treasuremap.

lb4368 commented 3 years ago

Moved to treasuremap

michaelfix commented 3 years ago

@sreejithpunnapuzha - Sreejith, are we close(r) to finishing?

sreejithpunnapuzha commented 3 years ago

I have looked into airshipctl and i dont see any dns entries that need to be registered. i have done the work to generate the dns configuration and start the container with that configuration. if i can get the list of dns entries that need to be registered, i can make the final changes and push the commit