Skip to content

Cluster context based clean up for Antrea Installation before delivering Antrea #5753

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

Open
Tracked by #6446
rajnkamr opened this issue Nov 29, 2023 · 4 comments
Open
Tracked by #6446
Labels
area/test/infra Issues or PRs related to test infrastructure (Jenkins configuration, Ansible playbook, Kind wrappers area/test/jenkins Issue about jenkins setup code kind/design Categorizes issue or PR as related to design. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@rajnkamr
Copy link
Contributor

rajnkamr commented Nov 29, 2023

Describe what you are trying to solve

Currently cleanup of Antrea Installation is done before Delivering Antrea to cluster, It is leading to cleaning of antrea installations on a test bed independent of cluster and hence interfere with existing cluster.
Describe the solution you have in mind

Handle Antrea CI clean up to allow deleting antrea installation based on cluster context and perform cleanup after successful run/failure
Describe how your solution impacts user flows

N/A
Describe the main design/architecture of your solution

Alternative solutions that you considered

Test plan

Additional context

@rajnkamr rajnkamr added kind/design Categorizes issue or PR as related to design. area/test/infra Issues or PRs related to test infrastructure (Jenkins configuration, Ansible playbook, Kind wrappers area/test/jenkins Issue about jenkins setup code labels Nov 29, 2023
@roopeshsn
Copy link
Contributor

Hi, @rajnkamr! I am interested in working on this issue. It'll be helpful if you provide more context on this issue.

Copy link
Contributor

github-actions bot commented May 5, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 5, 2024
@rajnkamr
Copy link
Contributor Author

closing this issue, for related info refer #5734

@rajnkamr rajnkamr reopened this Oct 25, 2024
@rajnkamr rajnkamr removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2024
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days. You can add a label "lifecycle/frozen" to skip stale checking.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 24, 2025
@rajnkamr rajnkamr added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test/infra Issues or PRs related to test infrastructure (Jenkins configuration, Ansible playbook, Kind wrappers area/test/jenkins Issue about jenkins setup code kind/design Categorizes issue or PR as related to design. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

2 participants