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

Using HTTP challenge provider results in pod stuck at ContainerCreating stage #455

Closed
tamalsaha opened this issue Sep 4, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@tamalsaha
Copy link
Member

commented Sep 4, 2017

From slack:
" Trying to create http ingress with certificate. Following this guide: https://github.com/appscode/voyager/blob/master/docs/user-guide/certificate/create.md#create-certificate-with-http-provider. After created the ingress, pod stuck at ContainerCreating stage because the xxxxxx-cert-secret-volume is not mounted. According to the guide, it suppose to be created after the cert resource is created. Looks like a chicken and egg problem. Did I miss anything? "

@xcompass

This comment has been minimized.

Copy link
Contributor

commented Sep 4, 2017

I'm using bare metal and kind of forced to use HTTP. And using k8s 1.7.3, voyager 3.2.0-rc1. Let me know if you need more info.

@xcompass

This comment has been minimized.

Copy link
Contributor

commented Sep 4, 2017

Here is the ingress and cert resource:

apiVersion: voyager.appscode.com/v1beta1
kind: Ingress
metadata:
  name: internal-services-ingress-controller
  namespace: default
  annotations:
    kubernetes.io/ingress.class: internal
    ingress.appscode.com/type: HostPort
    ingress.appscode.com/node-selector: '{ "role": "internallb" }'
    ingress.appscode.com/stats: 'true'
spec:
  tls:
    - secretName: mydomain-com-cert
      hosts:
      - mydomain.com
  rules:
  - host: mydomain.com
    http:
      paths:
      - backend:
          serviceName: mydomain-service
          servicePort: '8200'
apiVersion: voyager.appscode.com/v1beta1
kind: Certificate
metadata:
  name: mydomain-com-cert
  namespace: default
spec:
  domains:
  - mydomain.com
  email: myemail@mydomain.com
  provider: http
  httpProviderIngressReference:
    apiVersion: voyager.appscode.com/v1beta1
    kind: Ingress
    Namespace: default
    Name: internal-services-ingress-controller
@tamalsaha

This comment has been minimized.

Copy link
Member Author

commented Sep 4, 2017

Hi, what DNS registrar are you using?

@xcompass

This comment has been minimized.

Copy link
Contributor

commented Sep 4, 2017

I manage my own dns using a solution from BlueCat Networks. I manually created the domain name there.

@tamalsaha tamalsaha added this to the 4.0.0 milestone Sep 6, 2017

@tamalsaha

This comment has been minimized.

Copy link
Member Author

commented Sep 21, 2017

This is also addressed in #505

@tamalsaha

This comment has been minimized.

Copy link
Member Author

commented Sep 24, 2017

Fixed in #506

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.