rancher/k3k

expose config: Allow setting a loadBalancerClass in the loadbalancer config

Open

#860 opened on May 19, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (77 forks)auto 404
good first issueteam/collie

Repository metrics

Stars
 (886 stars)
PR merge metrics
 (PR metrics pending)

Description

Environmental Info: Host Cluster Version: not relevant

Node(s) CPU architecture, OS, and Version: not relevant

Host Cluster Configuration: I have a host cluster that has 2 loadbalancer implementation for different purposes.

K3K Cluster Configuration: not relevant

Describe the bug: If I want to spin up a k3k cluster and expose it via loadbalancer, k3k always picks the default implementation. I would like to be able to configure the desired loadBalancerClass in the cluster CRD.

See https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-class

Steps To Reproduce: In a cluster with two or more available loadBalancer implementations, create a shared cluster with the following spec:

apiVersion: k3k.io/v1beta1
kind: Cluster
  name: test-cluster
  namespace: testing
spec:
  expose:
    loadBalancer: {}
  mode: shared

Expected behavior: I can set the desired loadBalancerClass in the CRD.

Actual behavior: The controller tries to create a loadbalancer on the default loadbalancer implementation for the cluster.

Contributor guide

Research direction
Examine the K3K controller code for load balancer service creation, identify where the loadBalancerClass is set, and extend the Cluster CRD schema to include a loadBalancerClass field, then update the controller logic to use it.
Tech stack
gokubernetes
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes CRD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60