fix(misc): hostNetwork deployment when hostPort mismatches containerPort

[faust64]

trafficstars

• fixes hostNetwork configuration, when containerPort != hostPort
• fixes PodSecurityPolicy, when running privileged
• fixes rbac, when rbac.namespaced=true, access to ingressclass is defined
• adds --providers.kubernetescrd.allowcrossnamespace option to podTemplate, defaults to false, can be changed setting providers.kubernetesCRD.allowCrossNamespace=true. A default to false might be preferable, as Kubernetes Ingresses doesn't usually allow referring to resources in other namespaces. When you implement RBAC, maybe even NetworkPolicies: that does not sound like an option you would enable. Even though for sure, it could be useful in some chosen scenario.

Fixes #336

[faust64]

Anyone? Is there anything else I can do?

[faust64]

Also fixes #358

[rtribotte]

Hello @faust64,

Thanks for your work!

I wonder if you can split the fix for the issues #358/#499 in another PR, it would allow to separate concerns and move on faster, WDYT?

[mloiseleur]

Superseeded by #650