expose admin port of pulsar manager in service

[Mortom123]

See #438 / #438 (comment) 2.PR

Motivation

exposing Admin Port of Manager is needed in the future

Modifications

expose Admin Port of Manager

Verifying this change

• Make sure that the change passes the CI checks. See https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7629866629

[lhotari]

I already merged this, but I do have a concern. Since the admin port was added to the existing service that is a load balancer, I guess this expands the attack surface since admin operations are now accessible on the load balancer. @Mortom123 any thoughts on that?

[Mortom123]

@lhotari Mhh. You might be right. However I think the admij port gets deactivated / does not listen anymore once the account for the manager is created. But we could also make a second Node Port service I guess?

[lhotari]

@lhotari Mhh. You might be right. However I think the admij port gets deactivated / does not listen anymore once the account for the manager is created. But we could also make a second Node Port service I guess?

Yes I think it's better to reduce to possible exposure. One fact is that the Pulsar Helm Chart isn't following a "secure-by-default" principle currently. Anyhow we should attempt to improve the situation. I created #444 to cover other services, but I think that this admin port case could be handled outside of that.