Why is the Kubernetes pattern step 9.2 get primary_node_name failing with Status code is 404Summary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Firstly, we have PRB1968741, where we have added an extra failover step to support the OpenShift controller-manager endpoint. Before the fix, we were only targeting a fixed path: /api/v1/namespaces/kube-system/endpoints/kube-controller-manager But OpenShift uses a different namespace: /api/v1/namespaces/openshift-kube-controller-manager/endpoints/kube-controller-manager When the kube-controller-manager namespace is not present, the call returns 404, and the pattern does not attempt an alternative namespace. This was fixed with PRB1968741 by adding an extra failover step in the Reference to library "Kubernetes Leader" within the Kubernetes pattern: 9.3 failover - get primary_node_name for OpenShift In steps 9.2 and 9.3 to get primary node - we are querying the endpoint named "kube-controller-manager" (namespaces/kube-system/endpoints/kube-controller-manager) in the "kube-system" namespace and (namespaces/openshift-kube-controller-manager/endpoints/kube-controller-manager) in the "openshift-kube-controller-manager" namespace. We can check all endpoints in (namespaces/kube-system/endpoints), and if you are not able to see a "kube-controller-manager" endpoint, then the 404 error not found is an expected behaviour. To test this, you can run the 9.2 step by changing the resource to "namespaces/kube-system/endpoints" We need something like the following returned in the payload :"metadata":{"name":"kube-controller-manager"","namespace":"kube-system" Below is an example of the same API request via POSTMAN: An Endpoint object in Kubernetes:Stores the IP addresses of pods behind a Service. But since no Service exists, Kubernetes never created an Endpoint object.That means: There is no Service exposing kube-controller-manager. A Service needs to be created to expose these >> Customer should check on their Kubernetes setup.