You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder why hostnames are hardcoded within Ingress templates? It makes chart absolutely hard to provision without additional DNS sub-zone specifically for Astronomer.
My case:
In our k8s cluster, we already have a prometheus.<baseDomain> as well as a bunch of other similar components, included in the Astronomer Helm chart.
There is no way to overwrite the names:
So to be able to bootstrap Astronomer stack under custom domain names we need to provision an additional DNS sub-zone just for Astronomer, so DNS names won't conflict ...
The text was updated successfully, but these errors were encountered:
@CarpathianUA Interesting ideas, makes sense. I'd be happy to guide you through submitting a PR if you're interested in adding this feature. I'm not sure it will be prioritized otherwise. I've opened an internal issue so we can discuss and triage it.
@danielhoherd Due to the war between Ukraine and Russia I have very limited availability now (I'm from Ukraine). Would appreciate if you'll prioritize the issue internally - it would greatly increase deployment easiness for your customers.
Hello,
I wonder why hostnames are hardcoded within Ingress templates? It makes chart absolutely hard to provision without additional DNS sub-zone specifically for Astronomer.
My case:
In our k8s cluster, we already have a
prometheus.<baseDomain>
as well as a bunch of other similar components, included in the Astronomer Helm chart.There is no way to overwrite the names:
astronomer/charts/prometheus/templates/_helpers.yaml
Line 50 in f9e8ea7
astronomer/charts/astronomer/templates/ingress.yaml
Line 38 in f9e8ea7
So to be able to bootstrap Astronomer stack under custom domain names we need to provision an additional DNS sub-zone just for Astronomer, so DNS names won't conflict ...
The text was updated successfully, but these errors were encountered: