You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the kyverno cli with current version v1.11.4 on a kyverno-test.yaml using anchors fails with a message like this currently:
Test errors:
Path: ignore-delete-requests/kyverno-test.yaml
Error: error converting YAML to JSON: yaml: unmarshal errors:
line 43: key "policy" already set in map
line 44: key "rule" already set in map
line 45: key "namespace" already set in map
line 48: key "policy" already set in map
line 49: key "rule" already set in map
line 50: key "namespace" already set in map
line 53: key "policy" already set in map
line 54: key "rule" already set in map
line 55: key "namespace" already set in map
line 58: key "policy" already set in map
line 59: key "rule" already set in map
line 60: key "namespace" already set in map
line 63: key "policy" already set in map
line 64: key "rule" already set in map
line 65: key "namespace" already set in map
line 68: key "policy" already set in map
line 69: key "rule" already set in map
line 70: key "namespace" already set in map
line 73: key "policy" already set in map
line 74: key "rule" already set in map
line 75: key "namespace" already set in map
line 78: key "policy" already set in map
line 79: key "rule" already set in map
line 80: key "namespace" already set in map
line 83: key "policy" already set in map
line 84: key "rule" already set in map
line 85: key "namespace" already set in map
line 88: key "policy" already set in map
line 89: key "rule" already set in map
line 90: key "namespace" already set in map
line 93: key "policy" already set in map
line 94: key "rule" already set in map
line 95: key "namespace" already set in map
line 98: key "policy" already set in map,
line 99: key "rule" already set in map
line 100: key "namespace" already set in map
line 103: key "policy" already set in map
line 104: key "rule" already set in map
line 105: key "namespace" already set in map
line 108: key "policy" already set in map
line 109: key "rule" already set in map
line 110: key "namespace" already set in map
line 113: key "policy" already set in map
line 114: key "rule" already set in map
Test Summary: 0 tests passed and 0 tests failed
We were running the kyverno cli in version v1.10.4 before. This has been working without any issues. Drilling down the issue, I've seen that with the update we've made for the kyverno cli, we also updated:
k8s.io/apimachinery from v0.27.1 to v0.29.2 and with this
What I don't understand yet , is, why the functionality is lost. With my rudimentary knowledge of Go I understand that you forked the the goyaml.v2 and goyaml.v3 modules but currently rely on the goyaml.v2 module. The README.md files in the according subdirectory clearly state that goyaml.v2 includes support for anchors, but goyaml.v3 does not.
I could need support to actually understand what happened here. Also, are there any concrete plans to move to goyaml.v3 and to add support for anchors to goyaml.v3 then?
Thanks very much in advance for any help.
The text was updated successfully, but these errors were encountered:
Running the kyverno cli with current version v1.11.4 on a
kyverno-test.yaml
using anchors fails with a message like this currently:We were running the kyverno cli in version v1.10.4 before. This has been working without any issues. Drilling down the issue, I've seen that with the update we've made for the kyverno cli, we also updated:
k8s.io/apimachinery
fromv0.27.1
tov0.29.2
and with thissigs.k8s.io/yaml
fromv1.3.0
tov1.4.0
(The kubernetes apimachinery depends on this project, see https://github.com/kubernetes/apimachinery/blob/v0.29.1/pkg/util/yaml/decoder.go).
What I don't understand yet , is, why the functionality is lost. With my rudimentary knowledge of Go I understand that you forked the the
goyaml.v2
andgoyaml.v3
modules but currently rely on thegoyaml.v2
module. TheREADME.md
files in the according subdirectory clearly state thatgoyaml.v2
includes support for anchors, butgoyaml.v3
does not.I could need support to actually understand what happened here. Also, are there any concrete plans to move to
goyaml.v3
and to add support for anchors togoyaml.v3
then?Thanks very much in advance for any help.
The text was updated successfully, but these errors were encountered: