← 输入框|github.com|刷新
Skip to content

Juice Shop Helm Chart deployment fails when ingress is enabled #735

Closed

Description

@dhananjaya94

🐞 Bug report

Describe the bug

Helm Chart deployment fails when the ingress is enabled from the values.yaml

Steps To Reproduce

$ /usr/local/bin/helm repo add securecodebox https://charts.securecodebox.io/
"securecodebox" already exists with the same configuration, skipping
$ /usr/local/bin/helm repo update 
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "securecodebox" chart repository
Update Complete. ⎈Happy Helming!⎈
echo "
ingress:
  enabled: \"true\"
 " > values.yaml
$ /usr/local/bin/helm upgrade --install my-juice-shop securecodebox/juice-shop -f values.yaml --version 3.1.1 --dry-run --debug

Expected behavior

Helm3 Deployment should work

System (please complete the following information):

  • secureCodeBox Version/Release v12.7.0
  • Helm Chart Version 3.1.1
  • Kubernetes Version
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
  • Helm Version
$ /usr/local/bin/helm versionversion.BuildInfo{Version:"v3.7.1", GitCommit:"1d11fcb5d3f3bf00dbe6fe31b8412839a96b3dc4", GitTreeState:"clean", GoVersion:"go1.16.9"}

-->

Screenshots / Logs

history.go:56: [debug] getting history for release my-juice-shop
Release "my-juice-shop" does not exist. Installing it now.
install.go:178: [debug] Original chart version: "3.1.1"
install.go:199: [debug] CHART PATH: /root/.cache/helm/repository/juice-shop-3.1.1.tgz

Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: apiVersion not set
helm.go:88: [debug] error validating "": error validating data: apiVersion not set
helm.sh/helm/v3/pkg/kube.scrubValidationError
        helm.sh/helm/v3/pkg/kube/client.go:631
helm.sh/helm/v3/pkg/kube.(*Client).Build
        helm.sh/helm/v3/pkg/kube/client.go:204
helm.sh/helm/v3/pkg/action.(*Install).RunWithContext
        helm.sh/helm/v3/pkg/action/install.go:275
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:265
main.newUpgradeCmd.func2
        helm.sh/helm/v3/cmd/helm/upgrade.go:124
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
unable to build kubernetes objects from release manifest
helm.sh/helm/v3/pkg/action.(*Install).RunWithContext
        helm.sh/helm/v3/pkg/action/install.go:277
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:265
main.newUpgradeCmd.func2
        helm.sh/helm/v3/cmd/helm/upgrade.go:124
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371

Additional context

N/A

Activity

  1. rfelber commented on Oct 18, 2021

    @rfelber
    Member

    Hi @dhananjaya94

    welcome 👋 and thx for raising this bug issue 👍🏻

    This issue is already fixed (PR #698) in our main branch and will be resolved with our next release v3.2.0 very soon 🤞

  2. added this to the v3.2.0 milestone on Oct 18, 2021
  3. self-assigned this
    on Oct 18, 2021
  4. rfelber commented on Oct 19, 2021

    @rfelber
    Member

    The new version v3.2.0 is released and this issue should be fixed now 👍🏻 Therefore closing this issue.

    Please comment or reopen if you any further problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions