Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to run task when using custom TLS certificate

See original GitHub issue

Describe the bug

I have deployed Che on minikube. I am using a custom TLS certificate for Che endpoints.

That means that I have:

created a Kubernets tls secret with the key and certificate
updated CheCluster setting both spec/k8s/tlsSecretName and /spec/server/cheHostTLSSecret to point to that secret
add the CA certificate in configmap properly labelled (as described here)

When trying to run a task I get the following error:

Error launching task 'maven build': Request runTask failed with message: Failed to execute Che command: unable to verify the first certificate

Che version

nightly

Steps to reproduce

Deploy Che on minikube using chectl Configure Che to use a custom certificate as described here Start the Java maven sample Try to start one of the 2 tasks provided

Expected behavior

The maven build should run successfully

Runtime

minikube

minikube version: v1.17.1
commit: 043bdca07e54ab6e4fc0457e3064048f34133d7e

Installation method

$  chectl update next && \
   chectl server:deploy \
       -p minikube

Environment

macOS

Issue Analytics

State:
Created 3 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

sleshchenkocommented, Mar 9, 2021

Why it is working with the origininal self-signed certificate that is generated when installing Che?

The difference I see: https://che-incubator.github.io/2021/02/01/@mario.loriedo-using-mkcert-to-locally-trust-eclipse-che-tls-certificates-ffaafe76e5d0.html creates CA into custom-certs cert

While default certs Che operator generated, are propagated over

    spec:
      containers:
      - env:
        - name: CHE_SELF__SIGNED__CERT
          valueFrom:
            secretKeyRef:
              key: ca.crt
              name: self-signed-certificate
              optional: true
        - name: CHE_GIT_SELF__SIGNED__CERT
        - name: CHE_GIT_SELF__SIGNED__CERT__HOST

from secret self-signed-certificate Custom certificates and Che Self-signed can be used on different ways.

0reactions

l0rdcommented, Mar 17, 2021

Closing as this issue as been solved. Although I am still not able to successfully run this scenario as I have found another bug 😡