-
Notifications
You must be signed in to change notification settings - Fork 3.8k
docs: BPFmasquarade usage for helm option is wrong #12219
Copy link
Copy link
Closed
Labels
area/documentationImpacts the documentation, including textual changes, sphinx, or other doc generation code.Impacts the documentation, including textual changes, sphinx, or other doc generation code.good-first-issueGood starting point for new developers, which requires minimal understanding of Cilium.Good starting point for new developers, which requires minimal understanding of Cilium.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.
Description
Metadata
Metadata
Assignees
Labels
area/documentationImpacts the documentation, including textual changes, sphinx, or other doc generation code.Impacts the documentation, including textual changes, sphinx, or other doc generation code.good-first-issueGood starting point for new developers, which requires minimal understanding of Cilium.Good starting point for new developers, which requires minimal understanding of Cilium.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.
Bug report
General Information
Cilium documentation and actual helm chart has simple mismatch with
bpfMasqueradeoption which should setenable-bpf-masqueradevalue for Kubernetes manifest configmap.How to reproduce the issue
According to referenced documentation:
helm template cilium cilium/cilium --version v1.8.0-rc4 --set global.bpfMasquerade=false |grep enable-bpf-masqueradeenable-bpf-masquerade: "false", but gotenable-bpf-masquerade: "true"Based on discussion in chat correct option should be
config.bpfMasqueradeinstead ofglobal.bpfMasquerade. However most of the helm keys start with prefixglobal.