Setup Issues

[stevenpall]

I can't seem to get a test ingress resource definition working using the existing guide here: https://github.com/appscode/voyager/tree/master/docs/user-guide. I applied api/extensions/tprs.yaml, and then hack/deploy/voyager-without-rbac.yaml (after setting $CLOUD_PROVIDER to aws).

This creates the voyager deployment successfully. I then attempt to create an ingress definition, e.g.:

apiVersion: voyager.appscode.com/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: default
spec:
  rules:
  - host: appscode.example.com
    http:
      paths:
      - backend:
          serviceName: test-service
          servicePort: '80'

This results in the following error: no kind "Ingress" is registered for version "ingress.voyager.appscode.com/v1beta1".

For reference, I am running the appscode/voyager:1.5.6 image on Kubernetes 1.5.4.

[stevenpall]

I should add that all resources appear to be correct:

kubectl get pods | grep voyager
voyager-operator-2840134682-2t5lj                       1/1       Running   0          1h

kubectl get services | grep voyager
voyager-operator          100.70.68.164    <none>             56790/TCP                    1h

kubectl get thirdpartyresources | grep voyager
certificate.voyager.appscode.com        Voyager by AppsCode - Secure Ingress Controller for Kubernetes   v1beta1
ingress.voyager.appscode.com            Voyager by AppsCode - Secure Ingress Controller for Kubernetes   v1beta1

kubectl get endpoints | grep voyager
voyager-operator                  100.77.194.81:56790

[tamalsaha]

We changed the api group to voyager.appscode.com (voyager 3.0.0) from appscode.com (voyager 1.5.6). Please install Voyager 3.0.0

[tamalsaha]

Please also see release notes for 3.0.0 https://github.com/appscode/voyager/releases

[stevenpall]

Hum, I tried deleting everything and then following this again exactly (which uses the 3.0.0 image): https://github.com/appscode/voyager/blob/3.0.0/docs/user-guide/README.md#deploying-voyager. I then tried applying the example ingress definition on that page:

apiVersion: voyager.appscode.com/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: default
spec:
  rules:
  - host: appscode.example.com
    http:
      paths:
      - path: '/testPath'
        backend:
          serviceName: test-service
          servicePort: '80'
          headerRule:
          - X-Forwarded-Host %[base]
          rewriteRule:
          - '^([^\\ :]*)\\ /(.*)$ \\1\\ /testings/\\2'
          backendRule:
          - 'acl add_url capture.req.uri -m beg /test-second'
          - 'http-response set-header X-Added-From-Proxy added-from-proxy if add_url'

Unfortunately, I'm still getting `no kind "Ingress" is registered for version "voyager.appscode.com/v1beta1". Any ideas? I feel like I'm doing something wrong.

[tamalsaha]

Hm. Do you think I can take a look at your screen? I have a zoom meeting: https://zoom.us/j/517962534

You can download zoom from https://zoom.us/download

[stevenpall]

I can't at the moment, but perhaps we could set something up in the coming days? Let me know what would work for you.

Thanks!

[tamalsaha]

Just ping me on our Slack https://slack.appscode.com/ . I am happy to take a look.

[stevenpall]

Prefect, will do.

On Fri, Jul 14, 2017 at 4:55 PM Tamal Saha notifications@github.com wrote:

Just ping me on our Slack https://slack.appscode.com/ . I am happy to take a look.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/appscode/voyager/issues/298#issuecomment-315465439, or mute the thread https://github.com/notifications/unsubscribe-auth/ACrPt8g4UCU3qUBA07OikJrlgGLq6L6hks5sN9WsgaJpZM4OYsK1 .

--

Steven Pall M: 416.884.7255 | E: mail@stevenpall.ca

[stevenpall]

I ended up getting this working by running kubectl create instead of kubectl apply. This appears to be a known issue: https://github.com/coreos/kube-prometheus/issues/24 (at least with v1.5.x).

I've successfully created the test ingress (voyager/hack/deploy/test-ingress.yaml), but I'm not actually seeing it listed as an ingress. e.g. kubectl get ingresses -n default | grep test returns nothing. Any ideas about what's going on?

[tamalsaha]

Try kubectl get ingress.voyager.appscode.com

[stevenpall]

Thanks, that worked. I'm going to go ahead and close this.