Expose NAT gateway IP in the shoot cluster

[pbochynski]

How to categorize this issue?

/kind enhancement

What would you like to be added:
Gardener can create multiple NAT Gateways: https://gardener.cloud/docs/extensions/infrastructure-extensions/gardener-extension-provider-azure/docs/usage-as-end-user/#example-shoot-manifest-zoned-with-nat-gateways-per-zone
Please expose NAT Gateway IP(s) in the shoot cluster using a custom resource or config map (e.g. shoot-info)

Why is this needed:
There is no simple way to figure out what is the IP address (addresses) of the NAT Gateway in the unified way (the only way is to use cloud provider API to figure it out).
Users need it for configuring IP whitelisting in various services.

Maybe you can reopen this proposal: gardener/gardener#3873

[gardener-prow]

@pbochynski: The label(s) area/todo cannot be applied, because the repository doesn't have them.

In response to this:

How to categorize this issue?

/area TODO
/kind enhancement

What would you like to be added:
Gardener can create multiple NAT Gateways: https://gardener.cloud/docs/extensions/infrastructure-extensions/gardener-extension-provider-azure/docs/usage-as-end-user/#example-shoot-manifest-zoned-with-nat-gateways-per-zone
Please expose NAT Gateway IP(s) in the shoot cluster using a custom resource or config map (e.g. shoot-info)

Why is this needed:
There is no simple way to figure out what is the IP address (addresses) of the NAT Gateway in the unified way (the only way is to use cloud provider API to figure it out).
Users need it for configuring IP whitelisting in various services.

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.

[kon-angelo]

@pbochynski We are considering exposing the infrastructure provider status as an additional field to the shoot status. Would that work as a way to access this information or do you specifically need this info to be exposed in the shoot cluster?

[pbochynski]

In our case (Kyma), we do not expose the garden project to end users, so they don't have access to the shoot status. It would be better to have it propagated to the shoot. But we also can do the replication ourselves. Having the IP in the shoot status will help anyway, as we don't have to use cloud provider APIs and use Gardener API as an abstraction on top.

[pbochynski]

It is still valid