-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathkind-config.yaml
More file actions
36 lines (36 loc) · 1.47 KB
/
Copy pathkind-config.yaml
File metadata and controls
36 lines (36 loc) · 1.47 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# kind cluster configuration for Beeper demo
# Creates a two-node cluster with port mappings for the demo UIs.
#
# Usage:
# kind create cluster --name beeper-demo --config kind-config.yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
#
# Access model:
# - Beeper UI is exposed as a NodePort pinned to 30050 (helm values-dev.yaml:
# ui.service.nodePort), so the mapping below makes http://localhost:5050
# reach it directly — no port-forward needed.
# - The OTel Shop frontend-proxy and Jaeger ship from the upstream
# opentelemetry-demo chart as ClusterIP services, so the 30080/30686
# mappings below only carry traffic once those components are exposed as
# NodePorts with matching nodePorts. Until then, reach them via
# `make demo-ui` (kubectl port-forward). See TODO in demo/otel-demo-values.yaml.
#
# NOTE: extraPortMappings are applied only at `kind create cluster`. Changing
# them requires recreating the cluster (`make demo-down && make demo-up`).
nodes:
- role: control-plane
extraPortMappings:
# Beeper UI (NodePort pinned to 30050 in helm values-dev.yaml)
- containerPort: 30050
hostPort: 5050
protocol: TCP
# OTel Shop frontend-proxy (needs NodePort 30080 exposure — see TODO above)
- containerPort: 30080
hostPort: 8080
protocol: TCP
# Jaeger UI (needs NodePort 30686 exposure — see TODO above)
- containerPort: 30686
hostPort: 16686
protocol: TCP
- role: worker