Skip to content

[v2][healthcheck] instance does not have IP of type \"PUBLIC\" when running with --private-ip #1360

Closed
#1366
Closed
[v2][healthcheck] instance does not have IP of type \"PUBLIC\" when running with --private-ip#1360
#1366
Assignees
enocom
Labels
priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Description

@daquinoaldo
daquinoaldo
opened on Aug 31, 2022

Bug Description

I get the following error on /readiness although I set the --private-ip flag.

Readiness failed: Config error: instance does not have IP of type \"PUBLIC\"

However, the connection works. It's just the /readiness endpoint that is failing.

How to reproduce

  1. Run with the --private-ip flag specifying an instance with no public IP
  2. curl localhost:9090/readiness

Environment

  1. GKE v1.23 with Workload Identity
  2. Cloud SQL Proxy version: docker container built from the v2.0.0.preview.0 tag, targeting Linux amd64

Activity

  1. daquinoaldo
    added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Aug 31, 2022
  2. blunderbuss-gcf
    assigned
    enocom
    on Aug 31, 2022
  3. daquinoaldo
    changed the title [-][v2] instance does not have IP of type \"PUBLIC\" when running with `--private-ip`[/-] [+][v2][healthcheck] instance does not have IP of type \"PUBLIC\" when running with `--private-ip`[/+] on Aug 31, 2022
  4. enocom
    added
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    on Aug 31, 2022

  5. enocom commented on Aug 31, 2022

    @enocom
    enocom
    on Aug 31, 2022
    Member

    Thanks for the report. This should be an easy fix.

  6. enocom
    added a commit that references this issue on Aug 31, 2022

    fix: pass dial options when checking connections

    6540f3a
  7. enocom
    closed this as completedin 0033c36on Sep 2, 2022

  8. daquinoaldo commented on Sep 2, 2022

    @daquinoaldo
    daquinoaldo
    on Sep 2, 2022
    Author

    Amazing, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions