-
Notifications
You must be signed in to change notification settings - Fork 62
Make Eirini apps work with our DNS #284
Comments
I currently got an Eirinix working for mutating the apps, pointing them to the kubecf custom DNS instances. |
For some context: there's some experimental code in https://github.com/SUSE/eirini-dns-aliases/tree/f0rmiga/initial-impl (the meat of which is https://github.com/SUSE/eirini-dns-aliases/blob/f0rmiga/initial-impl/pkg/extension/extension.go ). |
This is going to involved cloudfoundry-incubator/eirinix#40 — eirinix has really old quarks dependencies. (It still refers to |
If you need a quick fix for building it, here is what I did in https://github.com/SUSE/eirini-persi/blob/master/go.mod#L25 |
PR posted in SUSE/eirini-dns-aliases#1 Required changes to test:
- name: eirini-dns-aliases
repository: https://mook-as.github.io/eirini-dns-aliases/
version: v0.0.0-dev+10-gcc1efd5
condition: features.eirini.enabled
eirini-dns-aliases:
deployment:
eirini_namespace: eirini Test by hijacking into one of the eirini-deployed apps (eirini-ssh seems busted again for me), and run |
@andreas-kupries I believe #1275 is currently waiting on SUSE/eirini-dns-aliases#1 |
Ok then. Marking it as blocked was correct. |
Describe the bug
Since Eirini apps cannot resolve the DNS records from the kubecf coreDNS instance, credhub.servie.cf.internal becomes unreachable.
To Reproduce
Deploy kubecf with Eirini and check that credhub CATS suite doesn't pass.
Expected behavior
Eirini apps should be able to resolve the kubecf DNS entries. It may be possible with an EiriniX mutator.
Environment
All versions.
The text was updated successfully, but these errors were encountered: