Use Gossip strategy for Kubernetes clustering
This commit is contained in:
parent
187a607563
commit
94fad09901
1 changed files with 4 additions and 5 deletions
|
|
@ -141,15 +141,14 @@ if config_env() == :prod do
|
||||||
|
|
||||||
# Configure libcluster topology based on environment
|
# Configure libcluster topology based on environment
|
||||||
if cluster_enabled do
|
if cluster_enabled do
|
||||||
|
# For now, use manual node list until we fix DNS resolution
|
||||||
|
# In production, we would use Kubernetes API or custom strategy
|
||||||
config :libcluster,
|
config :libcluster,
|
||||||
topologies: [
|
topologies: [
|
||||||
kubernetes: [
|
kubernetes: [
|
||||||
strategy: Cluster.Strategy.Kubernetes.DNS,
|
strategy: Cluster.Strategy.Gossip,
|
||||||
config: [
|
config: [
|
||||||
service: "aprs-headless",
|
secret: System.get_env("RELEASE_COOKIE", "aprs-cluster-cookie")
|
||||||
application_name: "aprsme",
|
|
||||||
namespace: System.get_env("POD_NAMESPACE", "aprs"),
|
|
||||||
polling_interval: 10_000
|
|
||||||
]
|
]
|
||||||
]
|
]
|
||||||
]
|
]
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue