Michael Prentice

```sh $ kubectl describe service npm-verdaccio Name: npm-verdaccio Namespace: default Labels: app=npm-verdaccio app.kubernetes.io/instance=npm app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=verdaccio app.kubernetes.io/version=5.0.1 helm.sh/chart=verdaccio-4.0.0 Annotations: cloud.google.com/neg: {"ingress": true} cloud.google.com/neg-status: {"network_endpoint_groups":{"4873":"k8s1-328e1eab-default-npm-verdaccio-4873-f4839dd4"},"zones":["us-central1-a","us-central1-b"]} meta.helm.sh/release-name: npm meta.helm.sh/release-namespace: default Selector: app.kubernetes.io/instance=npm,app.kubernetes.io/name=verdaccio Type:...

> Are you using an ingress controller? I believe that I'm using [Container-native load balancing](https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#container-native_load_balancing). I'm not using a Shared VPC. My cluster is running `1.18.16-gke.2100`. Networking | Status --...

OK, I got something working finally! Simlar to https://github.com/verdaccio/charts/issues/48#issuecomment-763056794 I had to change the following in the Service: ```yaml ports: - port: 4873 protocol: TCP targetPort: http ``` to ```yaml...

And related to https://github.com/verdaccio/charts/issues/48#issuecomment-763065007 I tried updating the service to ```yaml ports: - port: 80 protocol: TCP targetPort: http ``` But that didn't work.

It seems like this should be `80` https://github.com/verdaccio/charts/blob/2e563d8e73495fd032afe6448fbcf9033cabf3f8/charts/verdaccio/values.yaml#L22

I did another full deployment with the following `values.yaml` and it succeeded even with leaving the `targetPort: http` in the service: ```yaml image: repository: verdaccio/verdaccio tag: 5.0.4 pullPolicy: IfNotPresent pullSecrets:...

I tried a few more deployments and I ended up having to manually override the service from ```yaml targetPort: http ``` to ```yaml targetPort: 4873 ``` to get things to...

I'm finding that I have to update `targetPort` from `http` to `4873` every single time that I do `helm upgrade` 😞

@noroutine thank you for looking into this. Indeed I do have the following ```yaml spec: containers: - image: verdaccio/verdaccio:5.0.4 imagePullPolicy: IfNotPresent livenessProbe: failureThreshold: 3 httpGet: path: /-/ping port: http scheme:...

I'm seeing that specifying `nameOverride: "npm"` and `fullnameOverride: "registry-staging"` still ends up with `name: verdaccio` being set in the deployment.