ljmotta opened a new issue, #2234:
URL: https://github.com/apache/incubator-kie-issues/issues/2234

   
   While setting up Kubernetes cluster with the Dev Deployments wizard on KIE 
Sandbox, the Ingress definition at:
   
`incubator-kie-tools/packages/online-editor/static/dev-deployments/kubernetes/cluster-config/kie-sandbox-dev-deployments-resources.yaml`
 fails to apply due to a validation error from the NGINX Ingress admission 
webhook. The current Ingress path uses a regex-like pattern with `pathType: 
Prefix`, which is being rejected. Changing pathType to `ImplementationSpecific` 
makes it work locally, but we need to confirm if this is the correct/expected 
value and whether an upstream change tightened validation rules.
   
   Command executed
   ```sh
   kubectl apply -f <(curl -k 
http://localhost:9001/dev-deployments/kubernetes/cluster-config/kie-sandbox-dev-deployments-resources.yaml)
   ```
   
   Observed error
   ```
   Error from server (BadRequest): error when creating "/proc/self/fd/11": 
admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: 
ingress contains invalid paths: path /kube-apiserver(/|$)(.*) cannot be used 
with pathType Prefix
   ```
   
   Current Ingress snippet
   
   ```yaml
   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: kube-apiserver-proxy
     namespace: default
     annotations:
       nginx.ingress.kubernetes.io/backend-protocol: HTTP
       nginx.ingress.kubernetes.io/rewrite-target: /$2
       nginx.ingress.kubernetes.io/ssl-redirect: "false"
   spec:
     rules:
       - http:
           paths:
             - path: /kube-apiserver(/|$)(.*)
               pathType: Prefix
               backend:
                 service:
                   name: kube-apiserver-proxy
                   port:
                     number: 8051
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to