-
Notifications
You must be signed in to change notification settings - Fork 977
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
Feature - CloudSQL pre-allocation private IP range and GKE Cluster ignore_change lifecycle hook. #1056
Feature - CloudSQL pre-allocation private IP range and GKE Cluster ignore_change lifecycle hook. #1056
Conversation
…-foundation-fabric into feature/cts-changes
FAST: add instructions for billing export to stage 0 README (GoogleCloudPlatform#1051) See merge request nwmworld/nwm-digital/modules/third-party/cloud-foundation-fabric!1
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Refactor as per suggestions in PR See merge request nwmworld/nwm-digital/modules/third-party/cloud-foundation-fabric!2
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.
This is good to go once the last comment has been addressed, thanks!!!
This PR add supports for :
CloudSQL - provide an allocated IP range for private access. In some situations organizations have a pre-allocated /24 to be used as the private IP CIDR for CloudSQL instances. The changes in this PR help supply a pre-allocated IP range for the primary and replica instance
GKE-Cluster - The default pool is deleted on initial cluster creation, however the next iteration of plan/ apply using the module looks at changes on boot_disk_kms_key and always attempts to re-create the cluster there by doing a destroy / create of the cluster and nodepool. Addition of the ignore_changes lifecycle hook for the boot_disk_kms_key on the nodepool prevents the cluster re-creation on a subsequent plan / apply.