General Connectivity and Understanding Issue with Peerd on AKS v1.31.8 #117
Description
Is your feature request related to a problem?
Hi there,
I'm currently experiencing both a general connectivity issue and a lack of clarity on how peerd is supposed to function in practice.
I have successfully deployed the DaemonSet in an AKS cluster (version v1.31.8). All peerd pods are up and running as expected.
However, I’m not seeing the expected log entries such as P2PConnected, or during benchmark testing, any indication of P2PActive or P2PFailed as outlined in your documentation.
Am I possibly overlooking something in the configuration?
When running benchmark tests to evaluate how images are served within the cluster, the performance is in some cases worse with peerd deployed than without it.
This makes me wonder whether I’ve misunderstood some core aspect of how peerd is intended to operate.
Here are some example log excerpts for reference (attached below)
Any clarification or guidance would be highly appreciated.
Best regards,
Andreas
output-all-peerd-pods-benchmark.txt
What solution do you propose?
.
What alternatives have you considered?
When testing with the Spegel project, everything worked as expected, and the benchmark tests showed a clear performance improvement in image retrieval.
That’s why I’m wondering whether I might have missed something in the configuration of the peerd DaemonSet?
Any additional context?
No response
Are you willing to submit PRs to contribute to this feature?
- Yes, I am willing to implement it.