Support deployment within a custom namespace

[nyechiel]

Some deployment model require installation of components within a specific Kubernetes namespace. For e.g, OpenShift Dedicated dictates that any add-on based offering needs to run on its own exclusive namespace, such as openshift-storage.

Today, we use submariner-operator by default, and I don't think that we validated a deployment (as well as other life cycle management events, such as upgrade, and metrics) with a different custom namespace.

• Custom broker ns by adding --namesapce flag to deploy-broker cmd and in BrokerSpec Depends on Add --broker-namespace flag to deploy-broker #1682
• Custom operator ns by adding --namespace flag to join cmd and not store it in broker
• Relevant changes in operator, helm, bundle and packagemanifests

[dfarrell07]

Here's a little test showing changing the broker NS in the operator doesn't break anything: dfarrell07#1

[SteveMattar]

The namespace submariner-k8s-broker is a constant

submariner-operator/pkg/broker/namespace.go

Lines 30 to 38 in b52cf2d

	func NewBrokerNamespace() *v1.Namespace {
	ns := &v1.Namespace{
	ObjectMeta: metav1.ObjectMeta{
	Name: SubmarinerBrokerNamespace,
	},
	}
	return ns
	}

[stale]

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

[skitt]

This is required to support multiple clustersets in OCM.

[nyechiel]

@skitt @donaldh is this actually done now or do we have any other gaps to track?

[skitt]

@skitt @donaldh is this actually done now or do we have any other gaps to track?

We still have hard-coded namespaces in various places, e.g. https://github.com/submariner-io/submariner-operator/blob/devel/internal/constants/constants.go#L24

[github-actions]

This PR/issue depends on:

• Add --broker-namespace flag to deploy-broker #1682
  By Dependent Issues (🤖). Happy coding!

[nyechiel]

Done.