You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/12/07 03:59:19 UTC

[GitHub] [apisix-helm-chart] wofr opened a new issue, #409: help request: Declarative deployed routes are not added anymore (0.11.3 helm)

wofr opened a new issue, #409:
URL: https://github.com/apache/apisix-helm-chart/issues/409

   ### Description
   
   The following routes works fine when I use apisix 0.11.0 (helm deplyoment).  I do the deplyoment of the route in a declarative way.  When I switch to use apisxi 0.11.3 the deplyoment does not work anymore.  The only adaption I did on the route was use (apiVersion: apisix.apache.org/v2 instead of v2beta3)
   
   I do not really know what causes the problem the routes are simply not added to the gateway.  
   
    ```
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixTls
   metadata:
     name: {{ .Values.apisixTLSRoute }}
   #  namespace: apisix
   spec:
     hosts:
     - {{ .Values.hostName }}
     secret:
       name: {{ .Values.ingressSecret }}
       namespace: apisix
   ---
   # Define the route to access the backend
   apiVersion: apisix.apache.org/v2
   kind: ApisixRoute
   metadata:
     name: {{ .Values.apisixRoute }}
   #  namespace: apisix
   spec:
     http:
     - name: {{ .Values.hostName }}
       match:
         paths:
         - /*
         - /graphql
         hosts:
         - {{ .Values.hostName }}
       backends:
       - serviceName: {{ .Values.service }}
         servicePort: {{ .Values.appPort }}
       websocket: true
       
       plugins:
        - name: cors
          enable: true
        - name: redirect
          enable: true
          config:
            http_to_https: true       
        - name: openid-connect
          enable: true
          config:
            access_token_in_authorization_header: true
            bearer_only: false
            # When set to true, verifies the identity provider's SSL certificates. 
            ssl_verify: false
            client_id: "apisix"
            # Encrypt secret
            # Secret need to correspond with the secret defined in keycloak
            client_secret: "XXXXXXXXXXXXXXXX"
            disable: false
            discovery: "https://XXXXXXXXXXXXXXXXXXXXXXXXXX"
            realm: "XXXXXXXXXXX_staging"
            redirect_uri: "/callback"
            session:
              secret: {{ .Values.secretTokenKey }}
   ```
   
   ### Environment
   
   - APISIX version (run `apisix version`): /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua version 2.15.1
   - Operating system (run `uname -a`): Linux apisix-staging-8589bc6d9-w26wt 5.10.133+ apache/apisix#1 SMP Sat Sep 10 14:54:12 UTC 2022 x86_64 GNU/Linux
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant: 0.6.1
   


-- 
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: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] wofr commented on issue #409: help request: Declarative deployed routes are not added anymore (0.11.3 helm)

Posted by GitBox <gi...@apache.org>.
wofr commented on issue #409:
URL: https://github.com/apache/apisix-helm-chart/issues/409#issuecomment-1340642237

   With 0.11.1  its working!
   
   One funny observation I made, is that with 0.11.1 (and 0.11.0) the following call ist working and it does return the routes
   
   `kubectl exec -n apisix deploy/apisix-staging -- curl -s http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: MySecret'`
   
   With 0.11.2 (and 0.11.3)
   
   `kubectl exec -n apisix deploy/apisix-staging -- curl -s http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: MySecret'`
   I got the following error
   `error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "02bd185efd8594fb2e761f877be8974876c6b940701b3bc4be5d6496c552dd0b": OCI runtime exec failed: exec failed: unable to start container process: exec: "curl": executable file not found in $PATH: unknown`


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] tao12345666333 commented on issue #409: help request: Declarative deployed routes are not added anymore (0.11.3 helm)

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #409:
URL: https://github.com/apache/apisix-helm-chart/issues/409#issuecomment-1340609409

   Does 0.11.1 work fine?
   
   I think you should update the CRD file manually 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] wofr commented on issue #409: help request: Declarative deployed routes are not added anymore (0.11.3 helm)

Posted by GitBox <gi...@apache.org>.
wofr commented on issue #409:
URL: https://github.com/apache/apisix-helm-chart/issues/409#issuecomment-1340612805

   I did not try 0.11.1, I will do it by now.
   
   I dropped the whole deployment of apisix so the CRDs version should be fine


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org