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

[chectl] failed to install che with helm if k8s cluster has stable cert-manager #18962

Closed
3 tasks
sleshchenko opened this issue Feb 3, 2021 · 1 comment
Closed
3 tasks
Assignees
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@sleshchenko
Copy link
Member

Describe the bug

[chectl] failed to install che with helm if k8s cluster has stable cert-manager.

The easy solution I see - just upgrade cert-manager chectl uses to the stable one https://github.com/che-incubator/chectl/blob/master/installers/cert-manager.yml

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Run minikube.
  2. Install the stable cert-manager, like kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.4/cert-manager.yaml <- one which is used by devworkspace operator.
  3. Try to install Che with helm chart.

Expected behavior

Che is installed.

Actual behavoir

> chectl server:deploy -n che --multiuser --platform=minikube --installer=helm      % 16:57:16
› Current Kubernetes context: 'minikube'
  ✔ Verify Kubernetes API...OK
  ✔ 👀
    ✔ Verify if Eclipse Che is deployed into namespace "che"...it is not
  ✔ ✈️  Minikube preflight checklist
    ✔ Verify if kubectl is installed
    ✔ Verify if minikube is installed
    ✔ Verify if minikube is running
    ↓ Start minikube [skipped]
      → Minikube is already running.
    ✔ Check Kubernetes version: Found v1.20.2.
    ✔ Verify if minikube ingress addon is enabled
    ↓ Enable minikube ingress addon [skipped]
      → Ingress addon is already enabled.
    ✔ Retrieving minikube IP and domain for ingress URLs...192.168.39.241.nip.io.
    ✔ Checking minikube version... 1.17.1
    ↓ Check if cluster accessible [skipped]
  ✔ Following Eclipse Che logs
    ↓ Start following Operator logs [skipped]
    ✔ Start following Eclipse Che server logs...done
    ✔ Start following Postgres logs...done
    ✔ Start following Keycloak logs...done
    ✔ Start following Plugin registry logs...done
    ✔ Start following Devfile registry logs...done
    ✔ Start following namespace events...done
  ❯ 🏃
    ✔ Verify if helm is installed
    ✔ Check Helm Version: Found v3.3.4+ga61ce56
    ✔ Create Namespace (che)...does already exist.
    ❯ Check Eclipse Che TLS certificate...going to generate self-signed one
      ✔ Check Cert Manager deployment...already deployed
      ✔ Wait for cert-manager...ready
      ✔ Check Cert Manager CA certificate...already exists
      ✖ Set up Eclipse Che certificates issuer
        → the API version in the data (cert-manager.io/v1alpha2) does not match the expected API version (cert-manager.io/v1)
        Request certificate
        Wait for certificate
        Retrieving Che CA certificate
      Check Cluster Role Binding
      Preparing Eclipse Che Helm Chart
      Updating Helm Chart dependencies
      Deploying Eclipse Che Helm Chart
 ›   Error: Error: the API version in the data (cert-manager.io/v1alpha2) does not match the expected API version 
 ›   (cert-manager.io/v1)
 ›   Command server:deploy failed. Error log: /home/sleshche/.cache/chectl/error.log
@sleshchenko sleshchenko added kind/bug Outline of a bug - must adhere to the bug report template. area/chectl Issues related to chectl, the CLI of Che area/install Issues related to installation, including offline/air gap and initial setup labels Feb 3, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 3, 2021
@mmorhun mmorhun added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 3, 2021
@tolusha tolusha removed the area/install Issues related to installation, including offline/air gap and initial setup label Feb 4, 2021
@tolusha tolusha mentioned this issue Feb 16, 2021
57 tasks
@mmorhun mmorhun self-assigned this Feb 19, 2021
@mmorhun
Copy link
Contributor

mmorhun commented Feb 19, 2021

Should be fixed by che-incubator/chectl#1100

@tolusha tolusha modified the milestones: 7.27, 7.28 Feb 19, 2021
@tolusha tolusha closed this as completed Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants