Fixing deployment strategy issue

Ref: #18

Urgent bugfix for allocateLoadBalancerNodePorts for old Helm versions

With an older version of Helm (3.3.0) was reporting an issue with key validation. This fixes that.

Adding allocateLoadBalancerNodePorts support

Adding support for negating the allocateLoadBalancerNodePorts boolean, useful when you are using a load balancer on a cloud provider which is capable of direct IP routing.

See: https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/#ServiceSpec

allocateLoadBalancerNodePorts (boolean)

allocateLoadBalancerNodePorts defines if NodePorts will be automatically allocated for services with type LoadBalancer. Default is "true". It may be set to "false" if the cluster load-balancer does not rely on NodePorts. If the caller requests specific NodePorts (by specifying a value), those requests will be respected, regardless of this field. This field may only be set for services with type LoadBalancer and will be cleared if the type is changed to any other type.

Thanks @gitfool

What's Changed

• Add support for service allocateLoadBalancerNodePorts by @gitfool in #17

Full Changelog: 1.0.43...1.0.44

Adding service template annotations + shareProcessNamespace

• Supporting templating service annotations
• Adding shareProcessNamespace support