-
Notifications
You must be signed in to change notification settings - Fork 500
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
deploy: Modularize gcp terraform #717
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
|
||
maintenance_policy { | ||
daily_maintenance_window { | ||
start_time = "01:00" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then it would be better if users can customize the time, because 01:00 GMT is 9:00 Asia/Beijing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see how this get resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the no new line at end of file, I suggest you configure your editor to auto add new line at end of file when invoking save.
Yes I will do that going forward. I've been relying on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The file |
|
@@ -158,4 +158,11 @@ EOS | |||
KUBECONFIG = var.kubeconfig_path | |||
} | |||
} | |||
provisioner "local-exec" { | |||
when = destroy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does terraform say when updating the tidb-cluster? Will it be recreating which means destroying and creating again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case it does not destroy and create again if tidb-cluster changes. For a null_resource
as long as triggers
are not specified, or the ones that are specified don't change, then it should stay the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, cool! This is what we need.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
apply + destroy works well for me, as does the patch of the reclaim policy (no more orhpaned disks). |
cherry pick to release-1.0 failed |
@jlerche please open a cherry-pick to release-1.0 branch |
refactor of gcp terraform into modules * Add maintenance time variable with default * Changes bastion image to centos * Removes destroy trigger for patching reclaimpolicy PV * Adds bash script to change pv reclaimpolicy from Retain to Delete (cherry picked from commit 81fe851)
What problem does this PR solve?
Modularizes the GCP terraform script and uses released helm charts per #575
What is changed and how does it work?
Comprehensive refactor into modules so multiple tidb clusters can be managed
Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: