# Nodeport not being recongnized for rep set **URL:** \ **Category:** MongoDB\ **Tags:** kubernetes\ **Created:** [November 27, 2024, 12:23am UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293 "2024-11-27T00:23:44Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Henry\_Smearman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/henry_smearman/32/18339_2.png) [@Henry\_Smearman](https://forums.percona.com/u/Henry_Smearman)\ **Post date:** [November 27, 2024, 12:23am UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/1 "2024-11-27T00:23:44Z")
Hello All, I downloaded and started to use percona-helm-charts-psmdb-operator-1.18.0/charts/psmdb-db for my install, I was previously using 1.17.1. In 1.17.1 you could expose the rep set nodeport by using exposeType. In 1.18.0 it is only type ( see below ). After deploying when I check my services it is not using nodeport only ClusterIP. I tried to change type to exposeType in 1.18.0 but still no luck, any suggestions ? I only want to expose the rep set I have sharding disabled 1.17.1 ``` expose: enabled: true exposeType: NodePort ``` 1.18.0 ``` expose: enabled: true type: NodePort ``` ---
**Author:** ![eleonora.zinchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/eleonora.zinchenko/32/19132_2.png) [@eleonora.zinchenko](https://forums.percona.com/u/eleonora.zinchenko)\ **Post date:** [November 27, 2024, 8:38am UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/2 "2024-11-27T08:38:29Z")
Hi @Henry_Smearman , Could you describe the steps to reproduce and issue you face in more detail? I have tried to reproduce it but get the same behavior in both 1.17.1 and 1.18.0 - NodePort services are created for rs: 1.18.0: ```auto $ helm install helm-1180 percona/psmdb-db --version 1.18.0 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.type=NodePort $ k get service -w | grep helm-1180 helm-1180-psmdb-db-rs0 ClusterIP None 27017/TCP 104s helm-1180-psmdb-db-rs0-0 NodePort 34.118.229.21 27017:30870/TCP 103s helm-1180-psmdb-db-rs0-1 NodePort 34.118.226.186 27017:30797/TCP 77s helm-1180-psmdb-db-rs0-2 NodePort 34.118.225.52 27017:31415/TCP 49s ``` 1.17.1: ```auto $ helm install helm-1171-2 percona/psmdb-db --version 1.17.1 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.exposeType=NodePort $ k get service -w | grep helm-1171-2 helm-1171-2-psmdb-db-rs0 ClusterIP None 27017/TCP 11m helm-1171-2-psmdb-db-rs0-0 NodePort 34.118.227.74 27017:31036/TCP 11m helm-1171-2-psmdb-db-rs0-1 NodePort 34.118.238.124 27017:31273/TCP 10m helm-1171-2-psmdb-db-rs0-2 NodePort 34.118.239.32 27017:32035/TCP 10m ``` ---
**Author:** ![Henry\_Smearman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/henry_smearman/32/18339_2.png) [@Henry\_Smearman](https://forums.percona.com/u/Henry_Smearman)\ **Post date:** [November 27, 2024, 12:50pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/3 "2024-11-27T12:50:17Z")
Hello @eleonora.zinchenko , Thanks for your reply. I use the following to install. I download the helm charts from [https://github.com/percona/percona-helm-charts/archive/refs/tags/psmdb-operator-1.18.0.zip](https://github.com/percona/percona-helm-charts/archive/refs/tags/psmdb-operator-1.18.0.zip), deploy the operator and then deploy my rep set from charts/psmdb-db/ dir using the following command, helm install test118 . --version 1.18.0 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.type=NodePort. kubectl get services | grep test118 test118-psmdb-db-rs0 ClusterIP None 27017/TCP 31s test118-psmdb-db-rs0-0 ClusterIP 10.101.10.161 27017/TCP 30s test118-psmdb-db-rs0-1 ClusterIP 10.108.164.66 27017/TCP 15s test118-psmdb-db-rs0-2 ClusterIP 10.100.107.80 27017/TCP 5s ---
**Author:** ![eleonora.zinchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/eleonora.zinchenko/32/19132_2.png) [@eleonora.zinchenko](https://forums.percona.com/u/eleonora.zinchenko)\ **Post date:** [November 27, 2024, 2:07pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/4 "2024-11-27T14:07:20Z")
Hi @Henry_Smearman , > [@Henry\_Smearman](#): > > helm install test118 . --version 1.18.0 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.type=NodePort I can reproduce it only in case I leave a dot at the end of `NodePort` in command: The following command results in `ClusterIP` (note dot in the end): ```auto $ helm install test1182 . --version 1.18.0 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.type=NodePort. $ k get service |grep -w test1182 test1182-psmdb-db-rs0 ClusterIP None 27017/TCP 6m43s test1182-psmdb-db-rs0-0 ClusterIP 34.118.226.231 27017/TCP 6m41s test1182-psmdb-db-rs0-1 ClusterIP 34.118.231.58 27017/TCP 38s test1182-psmdb-db-rs0-2 ClusterIP 34.118.226.46 27017/TCP 6s ``` The following results in `NodePort`: ```auto $ helm install test118 . --version 1.18.0 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.type=NodePort $ k get service |grep -w test118 test118-psmdb-db-rs0 ClusterIP None 27017/TCP 7m38s test118-psmdb-db-rs0-0 NodePort 34.118.233.239 27017:31938/TCP 7m37s test118-psmdb-db-rs0-1 NodePort 34.118.231.111 27017:31623/TCP 7m8s test118-psmdb-db-rs0-2 NodePort 34.118.235.202 27017:32202/TCP 74s ``` Can you recheck that you do not pass anything extra like `.` or other symbols in command? ---
**Author:** ![Henry\_Smearman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/henry_smearman/32/18339_2.png) [@Henry\_Smearman](https://forums.percona.com/u/Henry_Smearman)\ **Post date:** [November 27, 2024, 2:22pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/5 "2024-11-27T14:22:22Z")
Hello @eleonora.zinchenko , Thanks for helping! I confirmed I do not have “.” at the end of the command. I copied your working command and still the issues persists. I have tried this on both my kub cluster and my minikube cluster, same results on both clusters. No issues with 1.17.1. helm install test118 . --version 1.18.0 --set sharding.enabled=false --set replsets.rs0.expose.enabled=true --set replsets.rs0.expose.type=NodePort kubectl get services | grep test118 test118-psmdb-db-rs0 ClusterIP None 27017/TCP 3m1s test118-psmdb-db-rs0-0 ClusterIP 10.103.228.228 27017/TCP 3m test118-psmdb-db-rs0-1 ClusterIP 10.104.65.58 27017/TCP 2m45s test118-psmdb-db-rs0-2 ClusterIP 10.96.220.29 27017/TCP 2m35s ---
**Author:** ![eleonora.zinchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/eleonora.zinchenko/32/19132_2.png) [@eleonora.zinchenko](https://forums.percona.com/u/eleonora.zinchenko)\ **Post date:** [November 27, 2024, 2:30pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/6 "2024-11-27T14:30:55Z")
Hi, That is strange. > deploy the operator and then deploy my rep set Can you describe how you deploy operator? Do you use 1.18.0 crd? ---
**Author:** ![Henry\_Smearman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/henry_smearman/32/18339_2.png) [@Henry\_Smearman](https://forums.percona.com/u/Henry_Smearman)\ **Post date:** [November 27, 2024, 2:37pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/7 "2024-11-27T14:37:54Z")
Hello, For the operator I install from the percona-helm-charts-psmdb-operator-1.18.0/charts/psmdb-operator dir . helm install operator . --version 1.18.0 kubectl get crds NAME CREATED AT [perconaservermongodbbackups.psmdb.percona.com](http://perconaservermongodbbackups.psmdb.percona.com) 2024-11-11T21:23:37Z [perconaservermongodbrestores.psmdb.percona.com](http://perconaservermongodbrestores.psmdb.percona.com) 2024-11-11T21:23:37Z [perconaservermongodbs.psmdb.percona.com](http://perconaservermongodbs.psmdb.percona.com) 2024-11-11T21:23:37Z ---
**Author:** ![eleonora.zinchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/eleonora.zinchenko/32/19132_2.png) [@eleonora.zinchenko](https://forums.percona.com/u/eleonora.zinchenko)\ **Post date:** [November 27, 2024, 2:50pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/8 "2024-11-27T14:50:15Z")
Hi, It seems you did not update 1.17.0 CRDs that is why new `type` is not used. I could reproduce your issue when using 1.17.0 CRD with 1.18.0 Operator. If you had old crds installed before installing 1.18.0 operator you need to “manually” update them. ```auto kubectl apply --server-side -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v1.18.0/deploy/crd.yaml kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v1.18.0/deploy/rbac.yaml ``` Please see [Upgrade MongoDB and the Operator - Percona Operator for MongoDB](https://docs.percona.com/percona-operator-for-mongodb/update.html#upgrade-via-helm) . ---
**Author:** ![Henry\_Smearman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/henry_smearman/32/18339_2.png) [@Henry\_Smearman](https://forums.percona.com/u/Henry_Smearman)\ **Post date:** [November 27, 2024, 3:06pm UTC](https://forums.percona.com/t/nodeport-not-being-recongnized-for-rep-set/35293/9 "2024-11-27T15:06:19Z")
Hello, Thanks so much! that was it ! kubectl get services | grep test118 test118-psmdb-db-rs0 ClusterIP None 27017/TCP 46s test118-psmdb-db-rs0-0 NodePort 10.111.49.138 27017:30770/TCP 46s test118-psmdb-db-rs0-1 NodePort 10.101.199.90 27017:30344/TCP 30s test118-psmdb-db-rs0-2 NodePort 10.109.64.12 27017:31574/TCP 20s