resolves "does not have a named port 'https' error

[jbarnes7952]

Fixes error for missing named port https

kubectl --namespace redpanda port-forward svc/redpanda-controller-operator-metrics-service 8443:8443
error: Pod 'redpanda-controller-operator-c897f85f9-sprxh' does not have a named port 'https'

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

John Barnes seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[RafalKorepta]

Hi,

Thanks for contribution.

Could you perform the following commands to generate change log and the helm template?

nix develop -c changie new
nix develop -c task generate

Please remember that changie is a interactive cli where you should choose first Redpanda Operator then Fix category and last the change log entry.

P.S. Could you sign our CLA?

[JFlath]

@RafalKorepta I think that's all sorted now - let me know if my meddling made things worse ;)

(FWIW, @jbarnes7952 did all the actual work. I just did a lot of git push --force until it looked right)

[RafalKorepta]

The problem here is that PR is opened from the fork. Our CI does not support this. I pushed changes to the feature branch within redpanda-operator repo and opened new PR #888 🤞 that I tests will pass :)