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

Documentation - helm chart version 0.3.3 crds validation failed #697

Closed
ksivamuthu opened this issue Sep 23, 2021 · 2 comments
Closed

Documentation - helm chart version 0.3.3 crds validation failed #697

ksivamuthu opened this issue Sep 23, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@ksivamuthu
Copy link
Contributor

Version

Karpenter: v0.3.3

Kubernetes: v1.20

Expected Behavior

  1. Installed the karpenter helm chart 0.3.3
  2. Add the provisioner with apiVersion: karpenter.sh/v1alpha4 as in documentation

Actual Behavior

The helm chart 0.3.3 has apiVersion: karpenter.sh/v1alpha3provisioner crd

Steps to Reproduce the Problem

Follow the steps in this documentation https://karpenter.sh/docs/getting-started/#install-karpenter-helm-chart

Install karpenter chart with version 0.3.3

helm upgrade --install karpenter karpenter/karpenter --namespace karpenter \
--create-namespace --set serviceAccount.create=false --version 0.3.3

Apply the provisioner

cat <<EOF | kubectl apply -f -
apiVersion: karpenter.sh/v1alpha4
kind: Provisioner
metadata:
name: default
spec:
provider:
 instanceProfile: KarpenterNodeInstanceProfile-${CLUSTER_NAME}
 capacityType: spot
 cluster:
   name: ${CLUSTER_NAME}
   endpoint: $(aws eks describe-cluster --name ${CLUSTER_NAME} --query "cluster.endpoint" --output json)
ttlSecondsAfterEmpty: 30
EOF
error: unable to recognize "STDIN": no matches for kind "Provisioner" in version "karpenter.sh/v1alpha4"
@ksivamuthu ksivamuthu added the bug Something isn't working label Sep 23, 2021
@ellistarn
Copy link
Contributor

We have a docs versioning issue. This will be possible in v0.3.4.

Until we have versioned docs, I don't think we have a choice but to leave docs change PRs open until we release.

@bwagner5
Copy link
Contributor

Will come up with docs versioning mechanism

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants