Conflict namespace resource when using kustomize

[oo00spy00oo]

What happened:

Error: accumulating resources: accumulation err='accumulating resources from 'kubernetes-gateway-api': '/workspace/bizzi-fluxcd/infrastructure/bizzi-dev/kubernetes-gateway-api' must resolve to a file': recursed accumulation of path '/workspace/bizzi-fluxcd/infrastructure/bizzi-dev/kubernetes-gateway-api': accumulating resources: accumulation err='accumulating resources from 'https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml': may not add resource with an already registered id: Namespace.v1.[noGrp]/gateway-system.[noNs]': evalsymlink failure on '/tmp/kustomize-1628085893/releases/download/v0.5.0/standard-install.yaml' : lstat /tmp/kustomize-1628085893/releases: no such file or directory

What you expected to happen:

Build with kustomize via command:

kustomize build

How to reproduce it (as minimally and precisely as possible):

kustomizaton.yaml

resources:
  - https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml  

Anything else we need to know?:

There are 2 kind: Namespace with name: gateway-system in standard-install.yaml

Remove conflict namespace resource

---
apiVersion: v1
kind: Namespace
metadata:
  name: gateway-system
---

[gyohuangxin]

This bug has been fixed by #1374, are you using the latest code?

[mclayer]

I think for non-contributors latest code = latest released code :)

[gyohuangxin]

@mclayer Yes, it's a good reminder. @robscott This fix was merged and cherry-picked to release-0.5, but we haven't updated it on release page.

[youngnick]

Yes, the fix for this will be included in the v0.5.1 patch release.

[gyohuangxin]

@youngnick Great, thanks!

[gyohuangxin]

@oo00spy00oo https://github.com/kubernetes-sigs/gateway-api/releases/tag/v0.5.1 was released, it fixed this issue.

[youngnick]

/close

[k8s-ci-robot]

@youngnick: Closing this issue.

In response to this:

/close

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.

[oo00spy00oo]

@oo00spy00oo https://github.com/kubernetes-sigs/gateway-api/releases/tag/v0.5.1 was released, it fixed this issue.

It's worked, thanks!