ArgoCD on a IPV6 preferred cluster? #21445
-
I'm trying to check Argo-CD installation in a IPV6 cluster Server and RepoServer have the following environment params, which are defaulted to 0.0.0.0. I can easily set these to "::" for IPV6 clusters My understanding is that the listen address for the servers should be But I could not find such params for Controller/AppSetController/Notifications controller. I thought that maybe the code itself is written to bind to IPv4/IPv6 or both if available. But, I came across some instances in the code base where 0.0.0.0 is hardcoded. argo-cd/controller/appcontroller.go Line 296 in b8508f2 Any suggestions on how to handle ArgoCD installation on a IPv6 preferred cluster? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I don't think this is important. In go binding to package main
import (
"net/http"
)
func main() {
http.ListenAndServe("0.0.0.0:8080", http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
w.Write([]byte("Hello, World!"))
}))
} I can access server using all this addresses
Swaping |
Beta Was this translation helpful? Give feedback.
I don't think this is important. In go binding to
0.0.0.0
or[::]
should bind to all interfaces. From quick test running this:I can access server using all this addresses
curl -v localhost:8080
curl -v [::1]:8080
curl -v 127.0.0.1:8080
curl -v 192.168.0.170:8080
curl -v [xxxx:xxxx:xxxx:xxxx:ed6a:f5be:99f:899e]:8080
curl -v [fe80::xxxx:xxxx:xxxx:xxxx%wlp1s0]:8080
Swaping
0.0.0.0:8080
for[::]:8080
or:8080
works same. But I didn't test Argo on IPv6 only cluster.