Is your feature request related to a problem? Please describe.
On my cluster, I have both local, on premises nodes as well as nodes running in cloud instances. The outpost deployments generated by the kubernetes integration does not support specifying a nodeSelector or affinity options.

Node placement is more of a concern when dealing with outposts that may need to be exposed outside the cluster, such as RADIUS or LDAP outposts, and where you ideally want their externalTrafficPolicy to be Local to preserve the requesting source IPs.

It might also be a concern if you're literally using the proxy outpost to... proxy... instead of using an external reverse proxy to forward-auth.

Describe the solution you'd like
Either allowing a nodeSelector or affinity to be specified as part of the outpost configuration.

Describe alternatives you've considered
Supporting a more generic jsonpatch/strategicMergePath approach to patching it.

Additional context