Closed joestringer closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has not seen any activity since it was marked stale. Closing.
It appears that StatefulSets operate differently enough in K8s environments that they can trigger some issues in Cilium, such as the following:
https://github.com/cilium/cilium/issues?q=is%3Aissue+statefulset+is%3Aopen
Currently we do not have any tests mentioning statefulsets in the tree. Expanding coverage over the use of StatefulSets may allow us to discover previously unknown issues and help to reproduce user reports.
From discussions on Slack, this seems like it will likely need some multi-node framework for doing lifecycle testing. We have infrastructure today doing this in different ways today:
There may be a few different paths for this, including: