quarkus.kubernetes.namespace should not be applied to clustered resources

[metacosm]

Describe the bug

If you use the quarkus.kubernetes.namespace property, it will get applied indiscriminately to all generated Kubernetes resources regardless of whether they actually can accept a namespace or not. While this usually doesn't cause issues with kubectl apply, other processes might be more regarding with respect to structure validation.

Expected behavior

Clustered resources should not have a namespace.

Actual behavior

All generated resources, including clustered ones, have their namespace field set.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @geoand (kubernetes), @iocanel (kubernetes)

[metacosm]

See for example: quarkiverse/quarkus-operator-sdk#964

[mcruzdev]

Hi @iocanel, I made a first research here and I think we need to solve it on dekorate side, am I right?

[mcruzdev]

Hi @metacosm @iocanel, I was wrong... It can be solved by kubernetes extension.

I created a pull request to solve it.