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

Prepare migration to IsovalentEgressGatewayPolicy resources #110

Merged
merged 2 commits into from
Apr 25, 2024

Conversation

simu
Copy link
Member

@simu simu commented Apr 25, 2024

We ensure that CiliumEgressGatewayPolicy resources aren't pruned automatically, so that we'll be able to migrate to IsovalentEgressGatewayPolicy resources without interruptions of egress traffic.

Checklist

  • The PR has a meaningful title. It will be used to auto-generate the
    changelog.
    The PR has a meaningful description that sums up the change. It will be
    linked in the changelog.
  • PR contains a single logical change (to build a better changelog).
  • Categorize the PR by adding one of the labels:
    bug, enhancement, documentation, change, breaking, dependency
    as they show up in the changelog.

@simu simu added the change label Apr 25, 2024
@simu simu force-pushed the prepare-egressgatewaypolicy-migration branch from 3489d66 to b829213 Compare April 25, 2024 11:04
@simu simu force-pushed the prepare-egressgatewaypolicy-migration branch from b829213 to 33db075 Compare April 25, 2024 11:21
@simu
Copy link
Member Author

simu commented Apr 25, 2024

Initial testing didn't show any negative impacts of having two copies of the same EgressGatewayPolicy in place at the same time. Probably still makes sense to do the migration in a planned maintenance window.

@simu simu marked this pull request as ready for review April 25, 2024 12:22
@simu simu requested a review from a team April 25, 2024 12:22
@simu simu merged commit 21d4c79 into master Apr 25, 2024
12 checks passed
@simu simu deleted the prepare-egressgatewaypolicy-migration branch April 25, 2024 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants