Feat(virtual-outbound): Add entity for virtual-outbound

[lahabana]

Summary

Virtual-outbounds enable users to define arbitrary hostnames.

It enables features like:

• Pod routing for stateful services
• Transition to Kuma without changing host names.

Documentation

• Link to the website documentation PR

Testing

• Unit tests
• E2E tests
• Manual testing on Universal
• Manual testing on Kubernetes

Backwards compatibility

• Add backport-to-stable label if the code is backwards compatible. Otherwise, list breaking changes.

This relies on changes not backported already.

[lahabana]

Do you want me to merge this without the implem behind it to make things more reviewable?

This only registers the new policy everywhere I'll then be able to connect it and add evaluation in a follow up PR.

[codecov-commenter]

Codecov Report

Merging #2576 (14084db) into master (12e56b9) will decrease coverage by 0.23%.
The diff coverage is 34.94%.

@@            Coverage Diff             @@
##           master    #2576      +/-   ##
==========================================
- Coverage   52.28%   52.05%   -0.24%     
==========================================
  Files         869      877       +8     
  Lines       48711    49454     +743     
==========================================
+ Hits        25470    25744     +274     
- Misses      21193    21644     +451     
- Partials     2048     2066      +18     

Impacted Files	Coverage Δ
api/mesh/v1alpha1/dataplane_helpers.go	80.91% <ø> (+0.66%)	⬆️
...ns/runtime/k8s/controllers/configmap_controller.go	9.84% <0.00%> (-1.27%)	⬇️
test/e2e/virtualoutbound/virtualoutbound_k8s.go	0.00% <0.00%> (ø)
...t/e2e/virtualoutbound/virtualoutbound_universal.go	0.00% <0.00%> (ø)
...est/framework/deployments/testserver/deployment.go	0.00% <0.00%> (ø)
...est/framework/deployments/testserver/kubernetes.go	0.00% <0.00%> (ø)
test/framework/interface.go	0.00% <0.00%> (ø)
test/server/cmd/echo.go	0.00% <0.00%> (ø)
test/framework/setup.go	1.17% <13.33%> (+1.17%)	⬆️
api/mesh/v1alpha1/virtual_outbound.pb.go	34.72% <34.72%> (ø)
... and 33 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 12e56b9...14084db. Read the comment docs.

[bartsmykla]

lgtm

[lobkovilya]

If I understand it correctly we require to add a parameter entry even if a tag has the same key as a parameter in gotemplate?
So if we have template:

host: {{ .foo }}.{{ .bar }}.{{ .baz }}

and we have DPP with inbound tags:

tags:
  foo: value1
  bar: value2
  baz: value3

Anyway I have to provide parameters section:

host: {{ .foo }}.{{ .bar }}.{{ .baz }}
parameters:
  - name: foo
  - name: bar
  - name: baz

Is it possible to resolve a template without explicit definitions of the parameters if no mapping required?

[lahabana]

This is what I wanted at first. However, the set of parameters is what enables me to build the right tags for the outbound on envoy.
I'm not sure it's feasible to extract the keys of the gotemplate but I can have a look.