Skip to content

gh: ipsec: support arbitrary number of nodes in ipsec-key-rotate action #32040

@julianwiedmann

Description

@julianwiedmann

In the per-tunnel key system, the ipsec-key-rotate action currently assumes a fixed number of nodes. This is tuned to the conformance-ipsec-e2e workflow - but doesn't support the conformance-eks workflow, which uses a different number of nodes. Thus the eks workflow currently doesn't test the per-tunnel key system.

We should improve the key-rotate action, so that it supports workflows with any number of nodes.

Metadata

Metadata

Assignees

Labels

area/CI-improvementTopic or proposal to improve the Continuous Integration workflowarea/encryptionImpacts encryption support such as IPSec, WireGuard, or kTLS.feature/ipsecRelates to Cilium's IPsec featurepinnedThese issues are not marked stale by our issue bot.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions