Fix 404 when using a tenant outside of the enmasse namespace

[ctron]

Type of change

• Bugfix

Description

Since the upgrade to fabric8, all IoT tests fail due to unknown tenants. It looks
like fabric8 changed it behavior, to apply a default namespace ot the client, which
makes the client only watch for tenants in the current namespace of the infrastructure.

This change explicitly enables "any" namespace.

Checklist

• Update/write design documentation in ./documentation/design
• Write tests and make sure they pass
• Update documentation
• Check RBAC rights for Kubernetes / OpenShift roles
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
• Reference relevant issue(s) and close them after merging
• Update CHANGELOG.md

[ctron]

@enmasse-ci run tests profile=iot

[ctron]

@enmasse-ci run tests profile=iot

[enmasse-ci]

❗ Build Failed ❗

[dejanb]

Tested the fix manually. It works again now.

[ctron]

Peeking at the console of the jenkins job, it also looks like the changes @k-wall made to the systemtests work. Let's wait for the tests to complete and with a bit of luck everything should be back 💚

[k-wall]

For the record, the regression when deleting an object loaded from a local resource fabric8io/kubernetes-client#1856

[enmasse-ci]

❌ Test Summary ❌

TEST_PROFILE: iot
TEST_CASE:
TOTAL: 34
PASS: 29
FAIL: 1
SKIP: 4

❗ Test Failures ❗

• testCreate in io.enmasse.systemtest.iot.isolated.IoTProjectManagedTest