Skip to content

WIP: Update to helm v2.16.0

James Fargher requested to merge helm_v2.16.0 into master

What does this MR do?

#35801 (closed)

Manual testing:

+ helm upgrade jupyter jupyter/jupyterhub --install --reset-values --tls --tls-ca-cert /data/helm/jupyter/config/ca.pem --tls-cert /data/helm/jupyter/config/cert.pem --tls-key /data/helm/jupyter/config/key.pem --version 0.9-174bbd5 --set 'rbac.create=true,rbac.enabled=true' --namespace gitlab-managed-apps -f /data/helm/jupyter/config/values.yaml
Release "jupyter" does not exist. Installing it now.
Error: no kind "Job" is registered for version "batch/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"

Retry:

+ helm upgrade jupyter jupyter/jupyterhub --install --reset-values --tls --tls-ca-cert /data/helm/jupyter/config/ca.pem --tls-cert /data/helm/jupyter/config/cert.pem --tls-key /data/helm/jupyter/config/key.pem --version 0.9-174bbd5 --set 'rbac.create=true,rbac.enabled=true' --namespace gitlab-managed-apps -f /data/helm/jupyter/config/values.yaml
Release "jupyter" does not exist. Installing it now.
Error: Could not get apiVersions from Kubernetes: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request
  • Deploy minimal-ruby-app and check with https

Screenshots

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by 🤖 GitLab Bot 🤖

Merge request reports