-
Notifications
You must be signed in to change notification settings - Fork 104
Cosmosdb autoscaling with migration #3918
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
Conversation
This script needs to work even if cosmos does not exists
5b1d3cb to
12f34c6
Compare
1e4c2b1 to
e66100f
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janboll, roivaz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-parallel |
1 similar comment
|
/test e2e-parallel |
|
/hold for the weekend, to not cause issues |
|
/test e2e-parallel |
|
/retest-required |
|
@janboll: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/test e2e-parallel |
https://issues.redhat.com/browse/AROSLSRE-400
What
Add a migration step before svc deployment.
Why
In order to enable autoscaling a migration of the container needs to be done. This adds a migration step before the cluster/svc resource creation. The script is idempotent (see log below) and can be run multiple times and also on missing rg/accounts for new environments. However the plan is to remove this once all cosmosdb have autoscaling enabled.
Special notes for your reviewer
Log showing that script works even if run multiple times: