hashicorp / hashicorp/vault-helm

Can not use this chart anymore on Kubernetes v1.20.6-34+e4abae43f6acde

Open
#514 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
1.3k
Forks
898
Avg merge
3d 1h
Merged PRs (30d)
1

Description

**Describe the bug**
While running this command
helm install -n vault vault ./

against microK8S version
Client:
Version: v1.3.7
Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175

Server:
Version: v1.3.7
Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175
UUID: 0cf02edb-151a-49c8-83e3-6272ee9101d3

I get this error
Error: chart requires kubeVersion: >= 1.14 which is incompatible with Kubernetes v1.20.6-34+e4abae43f6acde

**To Reproduce**
Steps to reproduce the behavior:
1. snap install microK8s --classic
3. checkout repo master branch
4. helm install -n vault vault ./
5. See error (vault logs, etc.)
Error: chart requires kubeVersion: >= 1.14 which is incompatible with Kubernetes v1.20.6-34+e4abae43f6acde

**Expected behavior**
Chart should be installed

**Environment**
MicroK8S
Client:
Version: v1.3.7
Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175

Server:
Version: v1.3.7
Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175
UUID: 0cf02edb-151a-49c8-83e3-6272ee9101d3
* vault-helm version:
master

**Additional context**
Downgrading to v0.10.0 everything is working fine

Contributor guide

Open the contributing guide

Research direction

Start with the chart metadata used by `helm install -n vault vault ./` and compare its Kubernetes version requirement with the reported microK8S version. Reproduce the install error, then verify that the chart installs successfully with the affected Kubernetes version while preserving compatibility with the working v0.10.0 behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.