-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wildcard ingress routing error #4067
Comments
@michael-riha This is a bug in translating route names in
|
@randmonkey appreciate your feedback, thank you. Just to make sure, this is how I would patch the default ...
- env:
- name: CONTROLLER_KONG_ADMIN_URL
value: https://127.0.0.1:8444
- name: CONTROLLER_KONG_ADMIN_TLS_SKIP_VERIFY
value: "true"
- name: CONTROLLER_PUBLISH_SERVICE
value: kong/kong-proxy
- name: POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
- name: CONTROLLER_FEATURE_GATES
value: CombinedRoutes=false
image: kong/kubernetes-ingress-controller:2.8
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 3
httpGet:
path: /healthz
port: 10254
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: ingress-controller
... So just on the Sources:
|
@michael-riha You do not need to turn of |
Is there an existing issue for this?
Current Behavior
When applying an
Ingress
with anamespace
-Issuer
I get this Error in the logsIssuer
Ingress
Expected Behavior
When I apply provided
Ingress
any subdomain such asShould be routed to the Service with SSL/TLS termination from
Kong
/KIC
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
I saw some wildcard related release notes
https://docs.konghq.com/gateway/3.3.x/how-kong-works/routing-traffic/#using-wildcard-hostnames
Not sure if this will fix it?
We can update if this is producing the error!
But ...
Latest
KIC
is2.9.3
... image: kong:3.2 ...
direct linkQuestion:
3.3.x
?KIC v2.9.3
with3.3.x
instead of3.2.x
which seems to be the preferred version?Thank you guys in advance!
The text was updated successfully, but these errors were encountered: