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

[Question] How to apply a kustomization containing helmCharts #4435

Closed
janbols opened this issue Jan 30, 2022 · 5 comments
Closed

[Question] How to apply a kustomization containing helmCharts #4435

janbols opened this issue Jan 30, 2022 · 5 comments
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@janbols
Copy link

janbols commented Jan 30, 2022

I followed the example described in https://github.com/kubernetes-sigs/kustomize/blob/master/examples/chart.md.
It creates a chart in the base dir.

I now want to apply the kustomization using kubectl apply -k dev. This gives the following:

➜  tmp.h6x5IPNa3Q kubectl apply -k dev               
error: accumulating resources: accumulation err='accumulating resources from '../base': '/tmp/tmp.h6x5IPNa3Q/base' must resolve to a file': recursed accumulation of path '/tmp/tmp.h6x5IPNa3Q/base': trouble configuring builtin HelmChartInflationGenerator with config: `
name: minecraft
releaseName: moria
repo: https://itzg.github.io/minecraft-server-charts
valuesInline:
  minecraftServer:
    difficulty: hard
    eula: true
    rcon:
      enabled: true
version: 3.1.3
`: must specify --enable-helm

How can I apply this kustomization? Specifying --enable-helm is not allowed and returns ...

➜  tmp.h6x5IPNa3Q kubectl apply -k dev --enable-helm
error: unknown flag: --enable-helm
See 'kubectl apply --help' for usage.

The only workaround now is to comment out the helmCharts section in the base kustomization.yml. Is this the way it should be?

@k8s-ci-robot
Copy link
Contributor

@janbols: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 30, 2022
@juame
Copy link

juame commented Feb 1, 2022

Hi @janbols
I guess this is related to the integration of kustomize in kubectl. See kubernetes/kubectl#1144.

@epcim
Copy link
Contributor

epcim commented Feb 1, 2022

KUSTOMIZE_ARG ?= --stack-trace --enable-alpha-plugins --load-restrictor LoadRestrictionsNone --enable-exec --enable-helm

you need --enable-alpha-plugins on older versions

otherwise today with KRM function, you can start using rendering outside of kustomize, example: https://github.com/epcim/gitops-infra/blob/master/cluster/sys/adguard/fnRenderHelm.yml

@KnVerey
Copy link
Contributor

KnVerey commented Feb 2, 2022

I guess this is related to the integration of kustomize in kubectl. See kubernetes/kubectl#1144.

This is correct. See the explanation on that issue, and #4401 for the longer term plan for Helm support.

/close

@k8s-ci-robot
Copy link
Contributor

@KnVerey: Closing this issue.

In response to this:

I guess this is related to the integration of kustomize in kubectl. See kubernetes/kubectl#1144.

This is correct. See the explanation on that issue, and #4401 for the longer term plan for Helm support.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

5 participants