Standardize cluster and components service exposure
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Eleonora Zinchenko October 9, 2024 at 10:46 AMEdited
Hi,
Reason for reopening - Cluster goes into error state if mongos.serviceperpod is enabled. New services are not created. To use servicePerPod cluster should be paused.
2024-10-08T11:47:16.439Z ERROR failed to reconcile cluster {"controller": "psmdb-controller", "object": {"name":"my-cluster-name","namespace":"default"}, "namespace": "default", "name": "my-cluster-name", "reconcileID": "900b8eaf-d22c-43ea-b455-67ea3b91e001", "replset": "rs0", "error": "failed to get mongos connection: ping mongo: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: , Type: Unknown, Last error: dial tcp: missing address }, { Addr: , Type: Unknown }, { Addr: , Type: Unknown }, ] }", "errorVerbose": "server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: , Type: Unknown, Last error: dial tcp: missing address }, { Addr: , Type: Unknown }, { Addr: , Type: Unknown }, ] }
2024-10-08T11:47:16.461Z ERROR Reconciler error {"controller": "psmdb-controller", "object": {"name":"my-cluster-name","namespace":"default"}, "namespace": "default", "name": "my-cluster-name", "reconcileID": "900b8eaf-d22c-43ea-b455-67ea3b91e001", "error": "reconcile statefulsets: failed to get mongos connection: ping mongo: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: , Type: Unknown, Last error: dial tcp: missing address }, { Addr: , Type: Unknown }, { Addr: , Type: Unknown }, ] }", "errorVerbose": "failed to get mongos connection: ping mongo: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: , Type: Unknown, Last error: dial tcp: missing address }, { Addr: , Type: Unknown }, { Addr: , Type: Unknown }, ]
Eleonora Zinchenko October 9, 2024 at 8:25 AM
Hi,
As discussed with @Slava Sarzhan : expose.externalTrafficPolicy
has fixed values in code that can not be overwritten. For this release we need to remove externalTrafficPolicy
from CR till the reason for fixed values is investigated in: https://perconadev.atlassian.net/browse/K8SPSMDB-1179
Done
Details
Assignee
dmitriy.kostiukdmitriy.kostiuk(Deactivated)Reporter
Sergey ProninSergey Pronin(Deactivated)Needs QA
YesNeeds Doc
YesStory Points
5Sprint
NoneFix versions
Priority
Medium
Details
Details
Assignee
dmitriy.kostiuk
dmitriy.kostiuk(Deactivated)Reporter
Sergey Pronin
Sergey Pronin(Deactivated)Needs QA
Yes
Needs Doc
Yes
Story Points
5
Sprint
None
Fix versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created August 15, 2022 at 11:00 AM
Updated November 14, 2024 at 5:21 PM
Resolved November 12, 2024 at 11:21 AM
Users who start using Percona Operators are confused as expose configuration is different in each operator. It is bad for onboarding and makes IaaC scripts more complex.
This improvement standardizes expose section in the Custom Resource as described in the spec document here