alibaba/GraphScope

[BUG] Use load balancer in CI, node port is bit hacky

Open

#2,444 opened on Feb 21, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (2,401 stars) (301 forks)batch import
component:dev-infragood first issue

Description

Describe the bug

Minikube and kind both have some load-balancer plugins, which would be more consitent with user's developing/production environments.

Contributor guide

Tech stack
dockerkubernetesgithub actions
Domain
devopsinfrastructureci cd
Issue type
bug
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic Kubernetes knowledgeFamiliarity with minikube or kind
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current CI configuration files (likely under .github/workflows or similar) to identify where node port is used. Research how to replace it with a load balancer using minikube's tunnel or kind's metallb plugin. Consider updating documentation if needed.