-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Well-defined vars never replaced changed output stream in 5.0.0 #5039
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Feb 8, 2023
/triage accepted |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Feb 16, 2023
I was able to reproduce this issue with the following setup:
If you run |
/assign |
jsitu777
added a commit
to awslabs/kubeflow-manifests
that referenced
this issue
Mar 20, 2023
upgrade this to fix this issue: kubernetes-sigs/kustomize#5039
jsitu777
added a commit
to jsitu777/kubeflow-manifests
that referenced
this issue
Mar 20, 2023
upgrade this to fix this issue: kubernetes-sigs/kustomize#5039
ryansteakley
pushed a commit
to ryansteakley/kubeflow-manifests
that referenced
this issue
Apr 14, 2023
upgrade this to fix this issue: kubernetes-sigs/kustomize#5039
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.
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What happened?
My project had a warning about well-defined vars never replaced. In 5.0.0 it appears that the stream which was used to write out that error changed from stderr to stdout. I was redirecting my output to a yaml file to be used later and this changed causes malformed yaml.
The error message looks like so
2023/02/08 08:28:59 well-defined vars that were never replaced: MY_PROJECT/ENV
What did you expect to happen?
Same behavior as 4.5.7 where the warning was written out to stderr.
How can we reproduce it (as minimally and precisely as possible)?
Expected output
Actual output
Kustomize version
5.0.0
Operating system
Linux
The text was updated successfully, but these errors were encountered: