Add flag to allow re-using of existing namespace

[AverageMarcus]

Currently it's not possible to use an existing namespace for hydrophone as it prompts you to run a cleanup if the provided namespace already exists.

It would be nice to have a flag similar to Sonobuoys --skip-preflight=existingnamespace that can instruct Hydrophone to use an existing namespace.

The reason for this is we generally run clusters with strict network policies enforced by default that prevents cross-namespace communication. To still allow the conformance tests to run and be triggered we need to create a CiliumNetworkPolicy within the conformance namespace but cannot do that before running hydrophone currently.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[AverageMarcus]

/remove-lifecycle stale