discuss: the design of yaml for APISIX

[apache]

discuss: the design of yaml for APISIX

[gxthrj]

ok, will change to english next week

[gxthrj]

ApisixPlugins has been reomved , plugins are value objects in route and service.
You can define plugin in ApisixRoute and ApisixService directly.
We also provide some annotations.
e.g.

apiVersion: apisix.apache.org/v1
kind: ApisixRoute
metadata:
  annotations:
    k8s.apisix.apache.org/cors-allow-headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,openID,audiotoken
    k8s.apisix.apache.org/cors-allow-methods: HEAD,GET,POST,PUT,PATCH,DELETE
    k8s.apisix.apache.org/cors-allow-origin: '*'
    k8s.apisix.apache.org/enable-cors: "true"
    k8s.apisix.apache.org/ssl-redirect: "false"
    k8s.apisix.apache.org/whitelist-source-range: 1.2.3.4,2.2.0.0/16
  name: httpserver-route
  namespace: cloud
spec:
  rules:
  - host: test1.apisix.apache.org
    http:
      paths:
      - backend:
          serviceName: api6
          servicePort: 80
        path: /test*
        plugins:
        - config:
            key: apisix-chash-key
            uri_args:
            - pId
            - userId|device
          enable: false
          name: aispeech-chash
      - backend:
          serviceName: httpserver
          servicePort: 8080
        path: /hello*
        plugins:
        - config:
            key: apisix-chash-key
            uri_args:
            - productId2
            - productId|deviceName
          enable: true
          name: aispeech-chash

[tao12345666333]

This issue is too old, and its content has been implemented. I will close it.
If we need a new design, a new discussion will be initiated.

Thanks!

[binlaniua]

建议增加 rewrite annotation

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
  name: rewrite
  namespace: default
spec:
  rules:
  - host: rewrite.bar.com
    http:
      paths:
      - backend:
          serviceName: http-svc
          servicePort: 80
        path: /something(/|$)(.*)

[gxthrj]

建议增加 rewrite annotation

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
  name: rewrite
  namespace: default
spec:
  rules:
  - host: rewrite.bar.com
    http:
      paths:
      - backend:
          serviceName: http-svc
          servicePort: 80
        path: /something(/|$)(.*)

@binlaniua ok，get it
We'll think about how to do it. maybe need a plugin in apisix

[Icedroid]

希望支持grpc

[membphis]

@gxthrj we need a English version

[Colstuwjx]

I have a question, why we create a new set of CRDs for implementing the ingress class, why not just use the official Ingress resource?

[tokers]

I have a question, why we create a new set of CRDs for implementing the ingress class, why not just use the official Ingress resource?

The offical Ingress resource is not so semantic in many use cases.

[Colstuwjx]

The offical Ingress resource is not so semantic in many use cases.

Totally understood.

BTW, I found we have one word in README mentioned about: Supports APISIX custom resources and Kubernetes native Ingress resources, do we have some best practises for switching from ingress-nginx to apisix?