push
github
fix(chart): correct ovs-ipsec-keys volume indentation and Talos IPSEC docs (#7041) * fix(chart): correct ovs-ipsec-keys volume indentation The ovs-ipsec-keys entry in the agent DaemonSet volumes list is indented two spaces deeper than its siblings, so it renders as a nested mapping of the preceding volume instead of a new list item. The result is invalid YAML and the chart fails to render whenever features.enableOvnIpsec is enabled: Error: YAML parse error on kube-ovn-v2/templates/agent/agent-daemonset.yaml: error converting YAML to JSON: yaml: line 263: did not find expected key The matching volumeMounts entry is already correct; only the volumes entry is affected. The flag defaults to false and no CI job sets it, which is why the chart shipped in this state. Signed-off-by: Aleksei Sviridkin <f@lex.la> * docs(chart): document the IPSEC key directory for Talos Linux Both charts describe a Talos install but list only two of the three host directories that must be moved off the read-only /etc filesystem. The IPSEC key directory was added later and kept the same /etc/origin default, so following the documented instructions and then enabling IPSEC leaves kube-ovn-cni in CreateContainerError: failed to mkdir "/etc/origin/ovs_ipsec_keys": mkdir /etc/origin: read-only file system The directory is configurable, so only the documented value list needs completing; no default changes here. Also annotate ovsIpsecKeysDirectory with the section its two neighbours already declare, so helm-docs groups it with them instead of listing it under Other Values. Signed-off-by: Aleksei Sviridkin <f@lex.la> --------- Signed-off-by: Aleksei Sviridkin <f@lex.la> (cherry picked from commit db1e2d00a)
14764 of 57168 relevant lines covered (25.83%)
0.3 hits per line