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

Release 0.5.0 contains duplicate kind:Namespace/gateway-system object definition. #1374

Closed
eigood opened this issue Sep 2, 2022 · 9 comments · Fixed by #1377
Closed

Release 0.5.0 contains duplicate kind:Namespace/gateway-system object definition. #1374

eigood opened this issue Sep 2, 2022 · 9 comments · Fixed by #1377
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@eigood
Copy link

eigood commented Sep 2, 2022

I'm attempting to reference either the standard-install.yaml or experimental-install.yaml on the releases page, via a kustomization.yaml/resources: tag. However, both of those files contain a duplicate definition of the gateway-system namespace. This breaks when applied directly via using via helmfile/helm/kustomize pipeline.

To work around this I downloaded the files and I modified them locally, to remove the duplicate Namespace.

@eigood eigood added the kind/bug Categorizes issue or PR as related to a bug. label Sep 2, 2022
@tokers
Copy link
Contributor

tokers commented Sep 4, 2022

What do you mean by saying a duplicate definition of the gateway-system? A re-defintion for Kubernetes namespace?

@robscott
Copy link
Member

robscott commented Sep 6, 2022

It looks like the problem is that both config/webhook/certificate_config.yaml and config/webhook/admission_webhook.yaml include the namespace definition. We concatenate those files together here:

for file in `ls config/webhook/*.yaml config/crd/experimental/gateway*.yaml`
do
echo "---" >> release/experimental-install.yaml
echo "#" >> release/experimental-install.yaml
echo "# $file" >> release/experimental-install.yaml
echo "#" >> release/experimental-install.yaml
cat $file >> release/experimental-install.yaml
done
for file in `ls config/webhook/*.yaml config/crd/standard/*.yaml`
do
echo "---" >> release/standard-install.yaml
echo "#" >> release/standard-install.yaml
echo "# $file" >> release/standard-install.yaml
echo "#" >> release/standard-install.yaml
cat $file >> release/standard-install.yaml
done
.

I don't think we're suggesting anyone use the individual YAML files, so it may make sense to pull out the namespace definition to a separate 0-namespace.yaml file.

@robscott robscott added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 6, 2022
@robscott robscott added this to the v0.5.1 milestone Sep 6, 2022
@gyohuangxin
Copy link
Member

@robscott I'm interesting in contributing to gateway-api project and I think this issue is a good start, can you assign it to me? Thanks.

@robscott
Copy link
Member

robscott commented Sep 6, 2022

Thanks!

/assign @gyohuangxin

@gyohuangxin
Copy link
Member

@robscott Thanks, I just created a PR, can you review it?

@robscott
Copy link
Member

Opening this back up to track a cherry pick into release-0.5

@gyohuangxin
Copy link
Member

@robscott I raised a PR to cherry pick it into release-0.5, please review it, thanks.

@mikemorris
Copy link
Contributor

/close

Cherry pick to 0.5 in #1387 has merged.

@k8s-ci-robot
Copy link
Contributor

@mikemorris: Closing this issue.

In response to this:

/close

Cherry pick to 0.5 in #1387 has merged.

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
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
6 participants