Does not work if workers are in different subnet.

[manishrajkarnikar]

I have workers spanning different subnet for security reasons. I see following error during the creation of unmanaged instance group. As a result, it cannot add any instance in the group

Requeuing "default/zoneprinter" due to error: [googleapi: Error 400: Resource 'projects/xxxx/zones/us-central1-b/instances/k8s-ig--xxxxxx' is expected to be in the subnetwork 'projects/xxxx/regions/us-central1/subnetworks/app-hosting-us-central1' but is in the subnetwork 'projects/xxxx/regions/us-central1/subnetworks/platform-us-central1'., wrongSubnetwork ....] (ingresses)

[nicksardo]

Can you describe your setup? Are you using multi-cluster or single cluster ingress?

[manishrajkarnikar]

@nicksardo I am using single cluster. But my masters are in different subnet than the workers.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions 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/test-infra repository.