Abdul Basit
Abdul Basit
@caseydavenport thank you for labeling it as high impact and hope to see it's resolved. I also edit the issue and added in the RFC link which talks about how...
Sounds like a plan. New logic with a different value like "auto" should work. Thank you so much and looking forward for the feature update :)
Okay hoping to see more IPv6 friendly contributions.
Thank you so much for the quick answer.
@caseydavenport thank you for looking in to the issue, it seems to be getting stuck. See below. Let me know if you need any more details. ``` docker logs ef870a87d78d...
@caseydavenport sorry for late response. The pod issue was resolved and will share the full logs once I find another pod in this state.
I noticed the same error in one of the cluster. {"caller":"net.go:268","component":"Memberlist","level":"error","msg":"memberlist: failed to receive: Encryption is configured but remote state is not encrypted from=[fd74:ca9b:3a09:868c:10:9:63:105]:29314","ts":"2024-03-04T04:18:33Z"} but with a very strange behavior....
I have two nodes cluster and I had prometheus running without any such error. Just reinstalled older version of prometheus and I start seeing logs again. I hope below is...
@raghs-aws thank you for sharing about this, I was looking in to migration from thin to thick plugin and was wondering exactly about this master-cni configs in the thick plugin....
Seems like there are are also manual options for masternetwork even in thick plugin, but still good to know about this flag to use if multusconfigs are set for auto....