Skip to content

Kubernetes cluster with 'terminating' pods #114

@aby2503

Description

@aby2503

Good evening. Can you help me. I'm using libcluster in Kubernetes with the strategy Cluster.Strategy.Kubernetes and libring for dynamic messaging

config :libcluster,
  topologies: [
    feed: [
      strategy: Cluster.Strategy.Kubernetes,
      config: [kubernetes_selector: "app=feed", kubernetes_node_basename: "feed"]
    ],
    fixture: [
      strategy: Cluster.Strategy.Kubernetes,
      config: [kubernetes_selector: "app=fixture", kubernetes_node_basename: "fixture"]
    ],
    web: [
      strategy: Cluster.Strategy.Kubernetes,
      config: [kubernetes_selector: "app=web", kubernetes_node_basename: "web"]
    ]
  ]

For some reason, sometimes after node moved to Terminating state, it still in cluster. Eventually, request to such node results in request timeout.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions