Skip to content
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.

GCP: Remove requirement for TARGET-INSTANCE object in AliasIP only use case #15

Closed
f5-applebaum opened this issue Feb 28, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@f5-applebaum
Copy link

Use case is that you would like to failover only AliasIps (vs Forwarding Rules).

Currently, the failover requires TARGET_INSTANCE objects to be created which is only needed for Forwarding Rules.

Workaround is creating target instance objects:

https://cloud.google.com/sdk/gcloud/reference/compute/target-instances/create

gcloud compute target-instances create NAME --instance=INSTANCE [--description=DESCRIPTION] [--instance-zone=INSTANCE_ZONE] [--zone=ZONE] [GCLOUD_WIDE_FLAG …]

@f5-applebaum
Copy link
Author

This is being tracked internally as:

AUTOSDK-195 - GCP: Remove requirement for TARGET-INSTANCE object in AliasIP only use case

@xags
Copy link

xags commented Mar 17, 2020

Could you give an example of this working? Creating the target-instances with the same name (for each F5) doesn't appear to do anything different. Would the declaration need anything removed/added to make this work? Is this also assuming that an internal LB is in-use? What if I am using default auto-created routes and not specifically defining them?

@alaari-f5
Copy link
Collaborator

Closing this issue

As of release CFE 1.2 we moved this CFE repo under F5Networks. Your issue was recreated there. To follow-up on this issue visit:

F5Networks/f5-cloud-failover-extension#11

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants