Description:

A namespace (say ns-1) contains DBaaSPolicy connectionNamespaces section pointing to another namespace (say ns-2). A provider account imported on ns-1 and updated with connectionNsSelector matchexpression to exclude ns-2 labels. The imported provider account on ns-1 visible under ns-2.

Expected Result:

Connection specifications mentioned on DBaaSInventory should have higher priority than the spec on DBaaSPolicy. Since the ns-1 spec connectioNSSelector has exclusion conditions for ns-2, the imported provider account details should not be pulled into ns-2.

Expecting the priority order in,

DBaaSPolicy ConnectionNSSelector << DBaaSPolicy ConnectionNamespaces << DBaaSInventory ConnectionNSSelector << DBaaSInventory ConnectionNamespaces

Actual Result:

The imported provider account details available on namespace

Screenshots:

DBaaSPolicy created with connectionNamespaces spec pointing to namespace - rr-project-adm01

DBaaSInventory created with connectionNSSelection spec to exclude the label key dbaas and the values stage and{} qe.

Namespace loaded with label dbaas=qe

The inventory rr-service-adm-crdb-1 available on +Add screen of project rr-project-adm01