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

Building kustomize v3 fails #4008

Closed
SteveMattar opened this issue Jun 22, 2021 · 5 comments
Closed

Building kustomize v3 fails #4008

SteveMattar opened this issue Jun 22, 2021 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@SteveMattar
Copy link

Describe the bug

I'm not able to build/install kustomize v3.10.0

Files that can reproduce the issue

go build -o /go/src/github.com/submariner-io/submariner-operator/bin/kustomize sigs.k8s.io/kustomize/kustomize/v3
# sigs.k8s.io/kustomize/api/internal/wrappy
vendor/sigs.k8s.io/kustomize/api/internal/wrappy/wnode.go:214:2: too many arguments to return
        have (map[string]interface {}, error)
        want (map[string]interface {})

Expected output

A working build.

Actual output

The error above.

Kustomize version
v3.10.0

Platform

Linux

Additional context

@SteveMattar SteveMattar added the kind/bug Categorizes issue or PR as related to a bug. label Jun 22, 2021
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 22, 2021
@k8s-ci-robot
Copy link
Contributor

@SteveMattar: 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.

@natasha41575
Copy link
Contributor

Is there a particular reason you need to use kustomize v3 and can't upgrade to v4?

@SteveMattar
Copy link
Author

@natasha41575 our project does not currently support v4. In future we will of course.

@strideynet
Copy link

I believe I am receiving a similar issue:

go get sigs.k8s.io/kustomize/kustomize/v3
go: downloading sigs.k8s.io/kustomize/kustomize/v3 v3.10.0
go: downloading sigs.k8s.io/kustomize/kustomize v0.0.0-20191024000301-ce7ebe3299dd
go: downloading sigs.k8s.io/kustomize/cmd/config v0.9.7
go: downloading github.com/olekukonko/tablewriter v0.0.4
go: downloading github.com/go-openapi/strfmt v0.19.5
go: downloading github.com/go-openapi/validate v0.19.8
go: downloading go.mongodb.org/mongo-driver v1.1.2
go: downloading github.com/go-openapi/errors v0.19.2
go: downloading github.com/go-openapi/runtime v0.19.4
go: downloading github.com/go-openapi/analysis v0.19.5
go: downloading github.com/go-openapi/loads v0.19.4
# sigs.k8s.io/kustomize/kustomize/v3/commands/build
../../../go/pkg/mod/sigs.k8s.io/kustomize/kustomize/[email protected]/commands/build/build.go:147:28: too many arguments in call to krusty.MakeKustomizer
        have (filesys.FileSystem, *krusty.Options)
        want (*krusty.Options)
../../../go/pkg/mod/sigs.k8s.io/kustomize/kustomize/[email protected]/commands/build/build.go:148:17: not enough arguments in call to k.Run
        have (string)
        want (filesys.FileSystem, string)
../../../go/pkg/mod/sigs.k8s.io/kustomize/kustomize/[email protected]/commands/build/build.go:202:26: too many arguments in call to "sigs.k8s.io/yaml".Marshal
        have (map[string]interface {}, error)
        want (interface {})

SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Jul 11, 2021
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Jul 27, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Jul 28, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Jul 28, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Jul 29, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Jul 29, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
@KnVerey
Copy link
Contributor

KnVerey commented Aug 4, 2021

Older releases aren't maintained by the community. We suspect that a dependency needs to be pinned. This is related to #3706: we want to vendor dependencies in the future for other reasons, which would also keep historical builds reproducible.

/close

@KnVerey KnVerey closed this as completed Aug 4, 2021
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Aug 30, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
SteveMattar pushed a commit to SteveMattar/submariner-operator that referenced this issue Sep 2, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
skitt pushed a commit to submariner-io/submariner-operator that referenced this issue Sep 3, 2021
This is a workaround until the issue will be fixed
kubernetes-sigs/kustomize#4008.

Signed-off-by: Steve Mattar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. 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