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

Setup Issues #298

Closed
stevenpall opened this issue Jul 14, 2017 · 11 comments

Comments

Projects
None yet
2 participants
@stevenpall
Copy link

commented Jul 14, 2017

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

This comment has been minimized.

Copy link
Author

commented Jul 14, 2017

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

This comment has been minimized.

Copy link
Member

commented Jul 14, 2017

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

This comment has been minimized.

Copy link
Member

commented Jul 14, 2017

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

@stevenpall

This comment has been minimized.

Copy link
Author

commented Jul 14, 2017

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

This comment has been minimized.

Copy link
Member

commented Jul 14, 2017

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

This comment has been minimized.

Copy link
Author

commented Jul 14, 2017

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

This comment has been minimized.

Copy link
Member

commented Jul 14, 2017

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

@stevenpall

This comment has been minimized.

Copy link
Author

commented Jul 14, 2017

@stevenpall

This comment has been minimized.

Copy link
Author

commented Jul 18, 2017

I ended up getting this working by running kubectl create instead of kubectl apply. This appears to be a known issue: coreos/kube-prometheus#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

This comment has been minimized.

Copy link
Member

commented Jul 18, 2017

Try kubectl get ingress.voyager.appscode.com

@stevenpall

This comment has been minimized.

Copy link
Author

commented Jul 19, 2017

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

@stevenpall stevenpall closed this Jul 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.