[
https://issues.jboss.org/browse/JBIDE-20096?page=com.atlassian.jira.plugi...
]
Paul Weil commented on JBIDE-20096:
-----------------------------------
External DNS for V3 is still the user's responsibility at this point. The way this
currently works with routes is:
1. If a user specifies a Host in the route the route will be created with that host used
as a key (via http headers or sni) to direct traffic from the router to the backends
2. If the user does not specify a Host in the route a host will be created for them using
a configurable post fix (this is configurable in the master.yaml). External DNS is still
up to the user, however in future use cases we will be able to register a wildcard DNS
entry based on the postfix to direct to the router(s) to provide default DNS services for
generated routes.
The sentence in the document pointed out above looks a bit misleading. I will update it.
Application wizard: creating eap-simple from templates and show in
browser tries to open 'eap.local'
----------------------------------------------------------------------------------------------------
Key: JBIDE-20096
URL:
https://issues.jboss.org/browse/JBIDE-20096
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 4.3.0.Beta2
not sure what is to "blame" here but creating app from
https://github.com/jboss-openshift/application-templates/blob/master/eap/...
(v3beta1) results in app getting created but show in browser wants me to go to
"eap.local" which pretty sure that is not something that exist from the outside.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)