Skip to content

Meaningful name/label for LoudBalancers #65

@guettli

Description

@guettli

Application LoadBalancers created by a Service are currently hard to associate to the corresponding service or cluster, when looking at the Hcloud UI.

Looking at the first two lines:

Image

It would be nice to have a more meaningful name, and Labels which reflect the source (cluster, service, ...).

Existing feature: Set annotation "load-balancer.hetzner.cloud/name" hetzner-cloud-controller-manager/docs/load_balancers.md

Tasks

Currently the name is like a173d00337ca64031a1645aae005f35f

Where does this name come from? Has this name a meaning?

What would be a good name, if no explicit name was given?

Check Upstream

Does Upstream handle that differently? Maybe they already solved that.

Does the CCM API allow better names

Does the CCM API to create LBs allow us to get the needed values like corresponding Cluster, Service, ...?

Check backward compatibility

If we give LBs a different name, will that be a breaking change?

Provide Feature to upstream?

When we implement that in our fork. Does it make sense to Merge the change to upstream, too?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions