Added --namespace flag to k3kcli policy create

[enrichman]

Fix #379

The --namespace flag was inherited by the global flags, but it was not used in the policy create command.

This PR change this behaviour, adding the option to provide multiple --namespace flags during the policy creation to actually bind it to existing namespaces:

-> % k3kcli policy create --mode=virtual --namespace k3k-mycluster --namespace k3k-mycluster2 --namespace k3k-myclusterXX virtual-policy
INFO[0000] Creating policy "virtual-policy"             
INFO[0001] Added policy "virtual-policy" to namespace "k3k-mycluster" 
INFO[0001] Added policy "virtual-policy" to namespace "k3k-mycluster2" 
WARN[0001] Namespace "k3k-myclusterXX" not found, skipping 

---

As suggested also a --overwrite flag was added. This is used to eventually overwrite existing policy. Without it we are not going to unbind existing policies, but just warn:

-> % k3kcli policy create --mode=virtual --namespace k3k-mycluster --namespace k3k-mycluster2 --namespace k3k-myclusterXX virtual-policy2 --overwrite
INFO[0000] Creating policy "virtual-policy2"            
INFO[0000] Policy "virtual-policy2" already exists      
INFO[0001] Found policy "virtual-policy" bound to namespace "k3k-mycluster". Overwriting it with "virtual-policy2" 
INFO[0001] Added policy "virtual-policy2" to namespace "k3k-mycluster" 
INFO[0001] Found policy "virtual-policy" bound to namespace "k3k-mycluster2". Overwriting it with "virtual-policy2" 
INFO[0001] Added policy "virtual-policy2" to namespace "k3k-mycluster2" 
WARN[0001] Namespace "k3k-myclusterXX" not found, skipping 

-> % k3kcli policy create --mode=virtual --namespace k3k-mycluster4 --namespace k3k-mycluster2 --namespace k3k-myclusterXX virtual-policy2 --overwrite
INFO[0000] Creating policy "virtual-policy2"            
INFO[0000] Policy "virtual-policy2" already exists      
INFO[0001] Added policy "virtual-policy2" to namespace "k3k-mycluster4" 
WARN[0001] Namespace "k3k-myclusterXX" not found, skipping 

[codecov-commenter]

Codecov Report

❌ Patch coverage is 24.48980% with 37 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.42%. Comparing base (2773030) to head (01791be).

Files with missing lines	Patch %	Lines
cli/cmds/policy_create.go	19.51%	31 Missing and 2 partials ⚠️
cli/cmds/policy_delete.go	25.00%	3 Missing ⚠️
cli/cmds/cluster_create.go	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #564      +/-   ##
==========================================
- Coverage   59.78%   59.42%   -0.36%     
==========================================
  Files          56       56              
  Lines        5217     5255      +38     
==========================================
+ Hits         3119     3123       +4     
- Misses       1811     1842      +31     
- Partials      287      290       +3     

Flag	Coverage Δ
cli	53.07% <24.48%> (-0.39%)	⬇️
controller	57.04% <0.00%> (-0.54%)	⬇️
e2e	57.04% <0.00%> (-0.54%)	⬇️
unit	36.32% <0.00%> (-0.27%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jp-gouin]

In case the namespace already has a policy attached. we should display a warning and not change the policy.
We can introduce a --overwrite flag to overwrite the current policy by the new one

[pmatseykanets]

Should we check if the policy was ever bound to one more namespaces and clear it when deleted?

[enrichman]

As discussed offline this should probably responsibility of the controller itself, I've opened an issue about this: #563

[pmatseykanets]

Seems like tests need some finessing due to message format changes.

[pmatseykanets]

May not be a good idea to use double quotes with a structured logger. IMHO it impairs readibility.

[enrichman]

Yep, the tests fails because when the cli is not running in a TTY it will output the logs in a structured format, while on the console it looks fine.

I'll move this to single quotes!