Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: cilium dualstack for load test pipeline #2603

Merged
merged 2 commits into from
Mar 4, 2024
Merged

Conversation

camrynl
Copy link
Contributor

@camrynl camrynl commented Feb 21, 2024

Reason for Change:

  • Creates a new stage for cilium dualstack in the load test pipeline
  • Added new parameters to the load test template in order to reuse stages and detect dualstack scenarios
  • Converted cilium/1.14 daemonset and operator files from .tpl to .yaml for consistency and fluid parameterization

Issue Fixed:

Requirements:

Notes:

@camrynl camrynl added the ci Infra or tooling. label Feb 21, 2024
@camrynl camrynl self-assigned this Feb 21, 2024
@camrynl camrynl requested a review from a team as a code owner February 21, 2024 19:45
@jpayne3506
Copy link
Contributor

I checked the CNI Release Test pipeline and did not see a passing Dualstack E2E. All other changes are 🟢

@vipul-21
Copy link
Contributor

lgtm, can we get a green on cni release pipeline ?

@camrynl
Copy link
Contributor Author

camrynl commented Feb 22, 2024

I can send the run where the dualstack stage passes, but I would also like to gather a fully green run with the latest changes once the pipeline is back up

@camrynl camrynl force-pushed the camrynl/loadtestds branch from fd12df5 to 0c0f8a7 Compare March 1, 2024 01:02
@camrynl camrynl added this pull request to the merge queue Mar 4, 2024
Merged via the queue into master with commit 4d90d23 Mar 4, 2024
89 checks passed
@camrynl camrynl deleted the camrynl/loadtestds branch March 4, 2024 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Infra or tooling.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants