This repository has been archived by the owner on Dec 10, 2021. It is now read-only.
disable autohealing by default #79
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 14, 2018
danisla
force-pushed
the
disable-autohealing
branch
from
13165b7
to
5098d83
Compare
danisla
force-pushed
the
disable-autohealing
branch
3 times, most recently
from
154e02c
to
51ce734
Compare
danisla
force-pushed
the
disable-autohealing
branch
from
51ce734
to
8dc7cf8
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Autohealing is currently a beta feature. When enabled, an HTTP health check is used to automatically recreate failed instances.
When enabled, the health check on the GCP side takes several many minutes to provision and often times out when creating. We will consider making this default enabled after the feature is GA.
In the meantime, if the instance fails for other reasons, it will be recreated automatically by the instance group manager.
Upgrading existing deployments to use this will fail because of: hashicorp/terraform-provider-google#1883
Upgrade workaround is to do the following steps: