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

Certificate not working #1567

Closed
lluunn opened this issue Sep 19, 2018 · 3 comments · Fixed by #1568
Closed

Certificate not working #1567

lluunn opened this issue Sep 19, 2018 · 3 comments · Fixed by #1568

Comments

@lluunn
Copy link
Contributor

lluunn commented Sep 19, 2018

I am seeing error in certificate:
ACME server does not allow selected challenge type or no provider is configured for domain

certificate spec:

spec:
    acme:
      config:
      - domains:
        - kfdeploy10.endpoints.kai-test2.cloud.goog
        http01:
          ingress: envoy-ingress

issuer spec:

spec:
    acme:
      email: lunkai@google.com
      privateKeySecretRef:
        key: ""
        name: letsencrypt-prod-secret
      server: https://acme-v02.api.letsencrypt.org/directory

I am guessing the http01: {} got trimmed from issuer spec

@lluunn
Copy link
Contributor Author

lluunn commented Sep 19, 2018

Result of doing ks show locally:

apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
  labels:
    ksonnet.io/component: vm
  name: letsencrypt-prod
  namespace: default
spec:
  acme:
    email: abc
    privateKeySecretRef:
      name: letsencrypt-prod-secret
    server: https://acme-v02.api.letsencrypt.org/directory

@lluunn
Copy link
Contributor Author

lluunn commented Sep 19, 2018

Verified after I patched the issuer with http01: , the certificate works now.

Issuer spec:

spec:
    acme:
      email: lunkai@google.com
      http01: {}
      privateKeySecretRef:
        key: ""
        name: letsencrypt-prod-secret
      server: https://acme-v02.api.letsencrypt.org/directory

@sambaiz
Copy link
Member

sambaiz commented Sep 19, 2018

#1544 includes a fix that resolve this issue.

@jlewi jlewi changed the title Certificate now working Certificate not working Sep 19, 2018
surajkota pushed a commit to surajkota/kubeflow that referenced this issue Jun 13, 2022
* Adding owners files

* adding required openshift scc

* Adding istio

* Adding istio

* Fixing kustomize

* adding cert-manager

* Adding Argo

* Adding cert manager

* Adding jupyter web app

* adding profiles and nb controller

* Adding components

* Adding Seldon

* Adding kfdef for openshift

* Fixing the fsgrp issue with nb controller

* Adding a patch for jnakfour in metadatadb

* moving openshift-scc to top

* Adding namespace in profiles

* Disabling tls in destination rule for pipeline ui

* Adding route

* Moving profiles and pipeline to top kustomize

* Adding new line

* Adding custom profile image to disable istio injection

* Updating profile image and istio scc

* Switching pipeline to generic and pulling out to application

Co-authored-by: Juana Nakfour <nakfour>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants