deckhouse / deckhouse/yandex-cloud-controller-manager

Unable to ensure load balancer due to service name

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
107
Forks
13
Avg merge
23h 39m
Merged PRs (30d)
1

Description

Hi, I'm trying to use ccm to setup load balancer, but service is failing to ensure load balancer with an error:

E1216 22:05:37.836237 1 controller.go:307] error processing service traefik/traefik (will retry): failed to ensure load balancer: rpc error: code = InvalidArgument desc = Validation failed:
- name: Field does not match the pattern /|[a-z][-a-z0-9]{1,61}[a-z0-9]/
I1216 22:05:37.836298 1 event.go:291] "Event occurred" object="traefik/traefik" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message="Error syncing load balancer: failed to ensure load balancer: rpc error: code = InvalidArgument desc = Validation failed:\n - name: Field does not match the pattern /|[a-z][-a-z0-9]{1,61}[a-z0-9]/"

It looks like kubernetes concatenates namespace and service and Yandex Cloud API doesn't allow such names.

cluster version: v1.21.6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file or test; start by tracing the load-balancer ensure path that handles the Kubernetes service name and the Yandex Cloud API validation error. Reproduce it with the traefik service in the traefik namespace, then verify that the resulting load balancer is accepted with a valid API name.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.