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
setting "dockersubdomain: true" breaks the ingress, at least for nginx in a EKS cluster. this is because the ingress gets the host "*.host.domain" but is missing the rule for the main site "host.domain", so when you navigate to the main site for nexus there will be a cert error. I had to use the additional rules to configure the docker subdomain rule instead.
Enabling "dockersubdomain: true" should probably just add an additional rule to also include "*.host.domain" along with "host.domain"
The text was updated successfully, but these errors were encountered:
Okay so I noticed if you do not enable " .Values.ingress.defaultRule" it will not create the rule for the main host. So "dockersubdomain: true" works fine, my bad I should have dug into the templates more first.
Is there a reason it defaults to false or why this is even a override ? I do not know why you would not want the rule for the main host for any reason.
I recommend at least updating the values with a comment or adding something into the readme explaining this better and setting the default to true.
setting "dockersubdomain: true" breaks the ingress, at least for nginx in a EKS cluster. this is because the ingress gets the host "*.host.domain" but is missing the rule for the main site "host.domain", so when you navigate to the main site for nexus there will be a cert error. I had to use the additional rules to configure the docker subdomain rule instead.
Enabling "dockersubdomain: true" should probably just add an additional rule to also include "*.host.domain" along with "host.domain"
The text was updated successfully, but these errors were encountered: