Skip to content
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

Ingress with multiple paths does not use plugin #93

Closed
eamonnmcevoy opened this issue Aug 16, 2018 · 1 comment
Closed

Ingress with multiple paths does not use plugin #93

eamonnmcevoy opened this issue Aug 16, 2018 · 1 comment

Comments

@eamonnmcevoy
Copy link

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.


Summary

SUMMARY_GOES_HERE

Kong Ingress controller version 0.0.5

Kubernetes version

Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:05:37Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Environment

  • Cloud provider or hardware configuration: AKS

What happened

Is it possible to configure multiple paths on a single ingress while using a plugin?

When I define separate KongPlugins and Ingresses, it works:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: my-ingress-A
  namespace: my-namespace
  annotations:
    jwt.plugin.konghq.com: my-plugin-jwt-A
spec:
  rules:  
    - host: localhost
      http:
        paths:
        - path: /routeA
          backend:
            serviceName: my-service-A
            servicePort: 80

---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: my-ingress-B
  namespace: my-namespace
  annotations:
    jwt.plugin.konghq.com: my-plugin-jwt-B
spec:
  rules:  
    - host: localhost
      http:
        paths:
        - path: /routeB
          backend:
            serviceName: my-service-B
            servicePort: 80

However, this is a bit cumbersome I would like to combine the ingresses and use one plugin CRD like so:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: my-ingress
  namespace: my-namespace
  annotations:
    jwt.plugin.konghq.com: my-plugin-jwt
spec:
  rules:  
    - host: localhost
      http:
        paths:
        - path: /routeA
          backend:
            serviceName: my-service-A
            servicePort: 80
        - path: /routeB
          backend:
            serviceName: my-service-B
            servicePort: 80

This issue is related to KongPlugin CRDs should be reusable , but I think this refers to using one plugin over multiple ingress definitions.

Is what I am attempting possible?
I still see all of the services and routes are created, just no plugins.

Expected behvaior

Each route should get an instance of the plugin

@eamonnmcevoy
Copy link
Author

I guess this belongs in Kong Nation. I'll close and ask there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant