[Bug]: example/custom-resources/cross-namespace-configuration missing secret namespace

[javorszky]

Version

edge

What Kubernetes platforms are you running on?

GKE Google Cloud

Steps to reproduce

While going through the example the VirtualServer kept coming up with error. Turns out that the VS is deployed in the cafe namespace, but the secret's definition does not contain the namespace, so that gets deployed to default.

This causes an issue where the VS can't make use of the secret, because it's in a different namespace.

Recommended fix

Change the command in the example to include the namespace:

- kubectl create -f cafe-secret.yaml
+ kubectl create -f cafe-secret.yaml -n cafe

The cafe-secret.yaml is a symlink, so we can't change the file contents without breaking other examples.

[github-actions]

Hi @javorszky thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[vepatel]

#7942 its fixed!