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

Current master version fails to request certificate #347

Closed
defcronyke opened this Issue Feb 25, 2018 · 18 comments

Comments

Projects
None yet
@defcronyke

defcronyke commented Feb 25, 2018

/kind bug

I tried using the master version to get a certificate from letsencrypt (staging and prod), and my Certificate resource never gets any events, the http challenge is never checked, and the secret is never created.

Doing the same on v0.2.3 works as documented.

Environment:

  • Kubernetes version (use kubectl version):
    Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.2-gke.1", GitCommit:"4ce7af72d8d343ea2f7680348852db641ff573af", GitTreeState:"clean", BuildDate:"2018-01-31T22:30:55Z", GoVersion:"go1.9.2b4", Compiler:"gc", Platform:"linux/amd64"}

  • Cloud provider or hardware configuration**: GCP

  • Install tools: Helm

  • Others: I set up cert-manager using instructions from this tutorial: https://github.com/ahmetb/gke-letsencrypt

@ahmetb

This comment has been minimized.

ahmetb commented Feb 25, 2018

It would be really great if you can provide:

  • kubectl logs from the cert-manager pod
  • kubectl get events in general while creating the Certificate object to see if any failures/warnings are logged.
@munnerz

This comment has been minimized.

Member

munnerz commented Feb 25, 2018

@defcronyke

This comment has been minimized.

defcronyke commented Feb 25, 2018

I don't have the logs anymore since getting it working, but the issue is reproducible because master version won't get you a cert currently.

@ahmetb

This comment has been minimized.

ahmetb commented Feb 27, 2018

I can repro. I just tried this on a brand new cluster and installed the chart from stable/cert-manager.

# cloned from ../kube/ingress.yaml, just added the tls section
# ideally use something like kinflate here to process the drop-in

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: web-http
  annotations:
    kubernetes.io/ingress.global-static-ip-name: "coffee"
spec:
  backend:
    serviceName: web-local
    servicePort: 8000
  tls:
  - secretName: coffeelog-web-tls
    hosts:
    - coffee.ahmet.im

---

apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: coffeelog-tls
  namespace: default
spec:
  secretName: coffeelog-web-tls
  issuerRef:
    name: letsencrypt-prod
    kind: ClusterIssuer
  commonName: coffee.ahmet.im
  dnsNames:
  - coffee.ahmet.im
  acme:
    config:
    - http01:
        ingress: web-http
      domains:
      - coffee.ahmet.im

events show no progress, as if it almost tries self-check only once:

Events:
  Type     Reason                 Age   From                     Message
  ----     ------                 ----  ----                     -------
  Warning  ErrorCheckCertificate  13m   cert-manager-controller  Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
  Normal   PrepareCertificate     13m   cert-manager-controller  Preparing certificate with issuer
  Normal   PresentChallenge       13m   cert-manager-controller  Presenting http-01 challenge for domain coffee.ahmet.im
  Normal   SelfCheck              13m   cert-manager-controller  Performing self-check for domain coffee.ahmet.im

cert-manager pod logs show no sign of activity, either

I0227 05:50:37.321873       1 helpers.go:165] Setting lastTransitionTime for Certificate "coffeelog-tls" condition "Ready" to 2018-02-27 05:50:37.321846331 +0000 UTC m=+1197.195264054
I0227 05:50:37.322244       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 05:50:37.326002       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 05:50:37.326342       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: [error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded, Operation cannot be fulfilled on certificates.certmanager.k8s.io "coffeelog-tls": StorageError: invalid object, Code: 4, Key: /registry/certmanager.k8s.io/certificates/default/coffeelog-tls, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 07bf1098-1b80-11e8-83fc-42010a80036a, UID in object meta: 9c7da06e-1b81-11e8-83fc-42010a80036a]
I0227 05:50:37.326990       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 05:50:37.327409       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 05:50:37.327588       1 sync.go:238] Preparing certificate with issuer
I0227 05:50:37.330046       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
@ahmetb

This comment has been minimized.

ahmetb commented Feb 27, 2018

The funny part is I wrote gke-letsencrypt tutorial with the same version of cert-manager (and the same chart as OP used here). I wonder what has changed that could cause this behavior. Let me know if you need access to a live cluster.

@ahmetb

This comment has been minimized.

ahmetb commented Feb 27, 2018

I gathered more info-level logs overnight:

I0227 05:50:37.326990       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 05:50:37.327409       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 05:50:37.327588       1 sync.go:238] Preparing certificate with issuer
I0227 05:50:37.330046       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
E0227 06:05:40.827193       1 prepare.go:167] Error cleaning up solver: [coffee.ahmet.im] Error cleaning up ingress: error cleaning up ingress: Ingress.extensions "web-http" is invalid: spec.rules[0].http.paths: Required value
I0227 06:05:40.827223       1 helpers.go:165] Setting lastTransitionTime for Certificate "coffeelog-tls" condition "Ready" to 2018-02-27 06:05:40.827215864 +0000 UTC m=+2100.700633579
I0227 06:05:40.827246       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 06:05:40.838591       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 06:05:40.838906       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 06:05:40.839246       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 06:05:40.839473       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 06:05:40.839762       1 sync.go:238] Preparing certificate with issuer
I0227 06:05:40.841529       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 06:20:42.830645       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 06:20:42.835138       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 06:20:42.835356       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 06:20:42.835493       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 06:20:42.835591       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 06:20:42.835681       1 sync.go:238] Preparing certificate with issuer
I0227 06:20:42.836214       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 06:35:44.864348       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 06:35:44.869698       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 06:35:44.869906       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 06:35:44.869994       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 06:35:44.870082       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 06:35:44.870174       1 sync.go:238] Preparing certificate with issuer
I0227 06:35:44.870725       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 06:50:46.830299       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 06:50:46.835267       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 06:50:46.835432       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 06:50:46.835531       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 06:50:46.835686       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 06:50:46.835776       1 sync.go:238] Preparing certificate with issuer
I0227 06:50:46.836337       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 07:05:49.061258       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 07:05:49.066198       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 07:05:49.066227       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 07:05:49.066264       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 07:05:49.066294       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 07:05:49.066319       1 sync.go:238] Preparing certificate with issuer
I0227 07:05:49.066763       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 07:20:53.195333       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 07:20:53.201076       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 07:20:53.201300       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 07:20:53.201491       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 07:20:53.201621       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 07:20:53.201719       1 sync.go:238] Preparing certificate with issuer
I0227 07:20:53.202233       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 07:35:57.384985       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 07:35:57.389681       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 07:35:57.389883       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 07:35:57.389972       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 07:35:57.390364       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 07:35:57.390493       1 sync.go:238] Preparing certificate with issuer
I0227 07:35:57.391038       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
I0227 07:51:00.301853       1 sync.go:242] Error preparing issuer for certificate: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
E0227 07:51:00.306071       1 sync.go:190] [default/coffeelog-tls] Error getting certificate 'coffeelog-web-tls': secret "coffeelog-web-tls" not found
E0227 07:51:00.306343       1 controller.go:196] certificates controller: Re-queuing item "default/coffeelog-tls" due to error processing: error waiting for key to be available for domain "coffee.ahmet.im": context deadline exceeded
I0227 07:51:00.306477       1 controller.go:187] certificates controller: syncing item 'default/coffeelog-tls'
I0227 07:51:00.306608       1 sync.go:107] Error checking existing TLS certificate: secret "coffeelog-web-tls" not found
I0227 07:51:00.306803       1 sync.go:238] Preparing certificate with issuer
I0227 07:51:00.307473       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30190771"
@gianrubio

This comment has been minimized.

Contributor

gianrubio commented Mar 7, 2018

I ran in the same issue today and using the image master-3666 solved

@Jarlotee

This comment has been minimized.

Jarlotee commented Mar 9, 2018

Same thing for me using kubernetes.io/tls-acme: "true"

I0309 21:53:05.176749       1 server.go:68] Listening on http://0.0.0.0:9402
I0309 21:53:05.177601       1 leaderelection.go:174] attempting to acquire leader lease...
I0309 21:53:21.228433       1 leaderelection.go:184] successfully acquired lease kube-system/cert-manager-controller
I0309 22:05:46.016841       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt-staging'
I0309 22:05:46.171774       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt-prod'
I0309 22:05:47.034485       1 helpers.go:122] Setting lastTransitionTime for ClusterIssuer "letsencrypt-staging" condition "Ready" to 2018-03-09 22:05:47.03447555 +0000 UTC m=+761.939664841
I0309 22:05:47.039952       1 controller.go:152] clusterissuers controller: Finished processing work item "letsencrypt-staging"
I0309 22:05:47.040042       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt-staging'
I0309 22:05:47.339057       1 helpers.go:122] Setting lastTransitionTime for ClusterIssuer "letsencrypt-prod" condition "Ready" to 2018-03-09 22:05:47.339049067 +0000 UTC m=+762.244238458
I0309 22:05:47.350267       1 controller.go:152] clusterissuers controller: Finished processing work item "letsencrypt-prod"
I0309 22:05:47.350369       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt-prod'
I0309 22:05:47.389770       1 controller.go:152] clusterissuers controller: Finished processing work item "letsencrypt-staging"
I0309 22:05:47.984318       1 helpers.go:122] Setting lastTransitionTime for ClusterIssuer "letsencrypt-prod" condition "Ready" to 2018-03-09 22:05:47.984303907 +0000 UTC m=+762.889493298
E0309 22:05:47.989437       1 controller.go:147] clusterissuers controller: Re-queuing item "letsencrypt-prod" due to error processing: Operation cannot be fulfilled on clusterissuers.certmanager.k8s.io "letsencrypt-prod": the object has been modified; please apply your changes to the latest version and try again
I0309 22:05:47.989481       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt-prod'
I0309 22:05:48.556450       1 controller.go:152] clusterissuers controller: Finished processing work item "letsencrypt-prod"
I0309 22:05:48.556552       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt-prod'
I0309 22:05:49.007585       1 controller.go:152] clusterissuers controller: Finished processing work item "letsencrypt-prod"
I0309 22:15:14.355903       1 controller.go:187] certificates controller: syncing item 'jenkins/tls-kubelego'
I0309 22:15:14.356596       1 sync.go:107] Error checking existing TLS certificate: secret "tls-kubelego" not found
I0309 22:15:14.356703       1 sync.go:238] Preparing certificate with issuer
I0309 22:15:14.357298       1 prepare.go:239] Compare "" with "https://acme-v01.api.letsencrypt.org/acme/reg/30836136"
@stuffandthings

This comment has been minimized.

stuffandthings commented Mar 13, 2018

Also getting the same issue. I've tried using canary and master-3666 but still getting the same problem with both builds

@ipedrazas

This comment has been minimized.

ipedrazas commented Mar 14, 2018

master-3781 still has that problem and you have to modify the ClusterRole and add ConfigMaps to it.

@daryllstrauss

This comment has been minimized.

daryllstrauss commented Mar 18, 2018

@ipedrazas Thank you! I spent days trying to figure out why I wasn't get a certificate and adding configmaps to the clusterrole fixed it.

@zolij

This comment has been minimized.

zolij commented Mar 21, 2018

I think I have the same problem. What is the solution exactly?

Thanks

@synoptase

This comment has been minimized.

synoptase commented Apr 6, 2018

Same here! I've noticed that the rbac.yml contains the configmaps property but my cert-manager role doesn't:

$ kubectl describe clusterrole cert-manager-cert-manager --all-namespaces
Name:         cert-manager-cert-manager
Labels:       app=cert-manager
              chart=cert-manager-0.2.4
              heritage=Tiller
              release=cert-manager
Annotations:  <none>
PolicyRule:
  Resources                          Non-Resource URLs  Resource Names  Verbs
  ---------                          -----------------  --------------  -----
  certificates.certmanager.k8s.io    []                 []              [*]
  clusterissuers.certmanager.k8s.io  []                 []              [*]
  endpoints                          []                 []              [*]
  events                             []                 []              [*]
  ingresses.extensions               []                 []              [*]
  issuers.certmanager.k8s.io         []                 []              [*]
  pods                               []                 []              [*]
  secrets                            []                 []              [*]
  services                           []                 []              [*]
  • yes, the role is named cert-manager-cert-manager
  • chart is version 0.2.4

I'm not familiar with RBAC, if someone could point how @daryllstrauss or @ipedrazas changed their cert-manager ClusterRole, i'd be grateful.

@madjam002

This comment has been minimized.

madjam002 commented Apr 6, 2018

@synoptase Make sure you use the helm chart in the contrib directory in this repo, not the official kubernetes/charts/stable repo, that one doesn't have ConfigMap in the cluster role.

In order to get everything working, I had to use the helm chart in this repo, along with opening firewall rules from my Kubernetes Nodes to allow access to the sites that I want TLS certificates for (my firewall was blocking traffic when cert-manager tried to access .well-known for the domain I wanted a certificate for).

@daryllstrauss

This comment has been minimized.

daryllstrauss commented Apr 6, 2018

Using the stable cert-manager.
@zolij @synoptase
Find your clusterrole. It'll be named cert-manager-HELMNAME
@synoptase From your output I can see you set the HELMNAME to cert-manager
kubectl get clusterrole --namespace kube-system | grep cert-manager
Once you have that you can edit it
kubectl edit clusterrole clusterrole/cert-manager-HELMNAME
You'll see a a few apiGroup sections. There first one is for cert-manager itself. The second is the general one.

- apiGroups:
  - ""
  resources:
  - secrets
  - events
  - endpoints
  - services
  - pods
  - configmaps
  verbs:
  - '*'

That's where I added configmaps to the end of the resources.

Changes to a recent version of kubernetes changed things requiring this update.

@synoptase

This comment has been minimized.

synoptase commented Apr 8, 2018

Thanks @madjam002 & @daryllstrauss, it worked.

@dhawal55

This comment has been minimized.

dhawal55 commented Apr 17, 2018

I'm using stable/cert-manager v0.2.9 and it has configmaps in the clusterRole, but I'm still getting the same error:

E0417 19:37:52.972868       1 controller.go:196] certificates controller: Re-queuing item "monitoring/alertmanager" due to error processing: [error waiting for key to be available for domain "alertmanager.g-fix-gke-p.dev.gcp.xxxxxxxx.com": context deadline exceeded, Operation cannot be fulfilled on certificates.certmanager.k8s.io "alertmanager": StorageError: invalid object, Code: 4, Key: /registry/certmanager.k8s.io/certificates/monitoring/alertmanager, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 742a8b94-4270-11e8-8c73-42010a8a00a2, UID in object meta: 6a81829d-4276-11e8-8c73-42010a8a00a2]

E0417 19:37:57.299775       1 controller.go:196] certificates controller: Re-queuing item "monitoring/prometheus2" due to error processing: [error waiting for key to be available for domain "prometheus.g-fix-gke-p.dev.gcp.xxxxxxxx.com": context deadline exceeded, Operation cannot be fulfilled on certificates.certmanager.k8s.io "prometheus2": the object has been modified; please apply your changes to the latest version and try again]

Here's how my clusterrole looks:

kubectl describe clusterrole cert-manager-cert-manager
Name:         cert-manager-cert-manager
Labels:       app=cert-manager
              chart=cert-manager-0.2.9
              heritage=Tiller
              release=cert-manager
Annotations:  <none>
PolicyRule:
  Resources                          Non-Resource URLs  Resource Names  Verbs
  ---------                          -----------------  --------------  -----
  certificates.certmanager.k8s.io    []                 []              [*]
  clusterissuers.certmanager.k8s.io  []                 []              [*]
  configmaps                         []                 []              [*]
  endpoints                          []                 []              [*]
  events                             []                 []              [*]
  ingresses.extensions               []                 []              [*]
  issuers.certmanager.k8s.io         []                 []              [*]
  pods                               []                 []              [*]
  secrets                            []                 []              [*]
  services                           []                 []              [*]

I'm using gke cluster v1.9.6-gke.1.

Here's my certificate:

apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
labels:
  app: alertmanager
  chart: prometheus
  identifier: null
metadata:
  clusterName: ""
  name: alertmanager
  namespace: ""
  resourceVersion: ""
  selfLink: /apis/certmanager.k8s.io/v1alpha1/namespaces/monitoring/certificates/alertmanager
  uid: ""
spec:
  acme:
    config:
    - domains:
      - alertmanager.g-fix-gke-p.dev.gcp.xxxxxxxx.com
      http01:
        ingress: alertmanager
  commonName: alertmanager.g-fix-gke-p.dev.gcp.xxxxxxxx.com
  dnsNames:
  - alertmanager.g-fix-gke-p.dev.gcp.xxxxxxxx.com
  issuerRef:
    name: letsencrypt
  secretName: alertmanager-certs
@munnerz

This comment has been minimized.

Member

munnerz commented May 9, 2018

This issue was originally opened as a new version of the chart was merged into master that removed an RBAC privilege (on endpoints) that was no longer required in the latest HEAD of the project.

Since then, we have moved to publishing the Helm chart from release branches so this should no longer be an issue.

In addition, we reverted the change that originally caused this issue in #343.

There are lots of different issues being reported here, that should be in their own issues as they are distinct bug reports.

I'm going to close this now, and if anyone is still running into problems, please open a new issue 😄

@munnerz munnerz closed this May 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment