Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Summary: Noticed that operators were actually struggling to update to the latest operator version... After doing some digging, it turns out it was unhappy because the latest operator version has new labels and deployment labels are immutable. luckily, we can still move forward and update from this case: operator-framework/operator-lifecycle-manager#952 OLM assumes the deployment name is the same, so it tries to do a rolling deploy. however, changing the deployment name indicates to OLM that we want to completely replace the deployment. suggestions for a better new deployment name are appreciated. also fixed a bug with the release build where the rc's prev versions were incorrect. Test Plan: created test plan in checklist for verifying operator updates, and ran through the test plan: https://www.notion.so/pixielabs/Operator-Release-Checklist-a705283f190c4c0aa127f9439bb34180 Reviewers: vihang, zasgar Reviewed By: vihang Differential Revision: https://phab.corp.pixielabs.ai/D9533 GitOrigin-RevId: 561964e
- Loading branch information