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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 clusterctl: only fix target namespace in template if TargetNamespace is set #5488

Merged
merged 1 commit into from
Oct 26, 2021

Conversation

sbueringer
Copy link
Member

@sbueringer sbueringer commented Oct 25, 2021

Signed-off-by: Stefan B眉ringer buringerst@vmware.com

What this PR does / why we need it:
In the generate yaml command we don't set a target namespace:

TargetNamespace: "",

Even though we don't set it, the NewTemplate func tries to fix the target namespace, i.e. it sets the namespace to an empty string.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5422

set

Signed-off-by: Stefan B眉ringer buringerst@vmware.com
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 25, 2021
@sbueringer sbueringer changed the title clusterctl: only fix target namespace in template if TargetNamespace is set 馃悰 clusterctl: only fix target namespace in template if TargetNamespace is set Oct 25, 2021
@sbueringer
Copy link
Member Author

/assign @fabriziopandini

Copy link
Member

@vincepri vincepri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 25, 2021
@fabriziopandini
Copy link
Member

Thanks for fixing this!
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 26, 2021
@k8s-ci-robot k8s-ci-robot merged commit 1e74421 into kubernetes-sigs:main Oct 26, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.1 milestone Oct 26, 2021
@sbueringer sbueringer deleted the pr-fix-yaml-gen branch October 26, 2021 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

clusterctl's yaml processor is generating invalid yamls when used on component manifests
4 participants