apolloconfig/apollo

helm3 方式部署k8s apollo nodeport端口无法自定义

Open

#4096 opened on Nov 12, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (29,769 stars) (10,177 forks)batch import
feature requesthelp wanted

Description

描述bug

通过helm3 安装apollo k8s服务。遇到个问题，就是无法指定暴露的NodePort端口。查了下issues没人问过

复现 image 如图，修改 values.yaml 加入type: NodePort 以及nodePort: 31809。 同时修改templates/service-configservice.yaml加入 nodePort: {{ .Values.configService.service.nodePort }} 如图： image 最后创建后结果 image

期望

希望可以指定NodePort端口号

截图

如果可以，附上截图来描述你的问题

额外的细节和日志

  • 版本： image k8s 1.18 helm3
  • 错误日志
  • 配置：
  • 平台和操作系统

Contributor guide

Tech stack
kubernetes
Domain
infrastructuredevops
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.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
HelmKubernetesYAML configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
The issue requests adding support for custom NodePort in the Apollo Helm chart. The user has modified values.yaml and the template file service configservice.yaml to add nodePort. To implement, one should add a configurable nodePort value in values.yaml (e.g., under configService.service.nodePort), then update the template to conditionally set nodePort when type is NodePort. Reference the chart's values.yaml and templates/service configservice.yaml files. No linked PRs or comments indicate prior work.