Skip to content
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.

Add ingress resource type to kubernetes targets provider. #469

Merged
merged 2 commits into from
Sep 16, 2020

Conversation

manugarg
Copy link
Contributor

No description provided.

As ingresses can have rules with multiple hosts and paths, ingress resources are named as follows:

<ingress_name> (if no rules at all)
<ingress_name>_<host> (if path is "/")
<ingress_name>_<host>__<path with / replaced by _>

We attach "fqdn" (=host) and "relative_url" (=path) labels to the resources if these labels are not set already. These labels can then be used inside HTTP probe for automatic configuration.

Implements: #419
PiperOrigin-RevId: 331914954
@manugarg manugarg added this to the v0.11.0 milestone Sep 16, 2020
@manugarg manugarg merged commit 928d3de into master Sep 16, 2020
@manugarg manugarg deleted the 63729A23134379909BFCA3AC3C378B48 branch September 16, 2020 03:34
@manugarg manugarg linked an issue Sep 16, 2020 that may be closed by this pull request
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature Request] Allow k8s to discover ingress resources
1 participant