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
Any component that uses pyyaml (like kubernetes.core.k8s in my case) is affected by the fact that pyyaml currently does not support YAML 1.2. One of the maintainers noted in an issue that we can use an alternative library (developed by him) as a workaround until pyyaml is updated to support YAML 1.2.
ISSUE TYPE
Use yamlcore on top of pyyaml until pyyaml support YAML 1.2 spec.
COMPONENT NAME
Every components that use pyyaml.
ADDITIONAL INFORMATION
In this reproducible example, my playbook applies a Kustomize file that deploys a Helm chart. In a production scenario, my Kustomize setup would include a Helm chart along with additional components. Why do I use Ansible this way instead of using the helm components? This is because I’m using the playbook only for the initial setup; after that, ArgoCD takes over and synchronizes changes to this Kustomize file.
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ^fatal: [master1.unicornafk.fr -> localhost]: FAILED! => changed=false msg: |- Failed to load resource definition: could not determine a constructor for the tag 'tag:yaml.org,2002:value' in "<unicode string>", line 9903, column 29:
The text was updated successfully, but these errors were encountered:
SUMMARY
Any component that uses
pyyaml
(likekubernetes.core.k8s
in my case) is affected by the fact thatpyyaml
currently does not support YAML 1.2. One of the maintainers noted in an issue that we can use an alternative library (developed by him) as a workaround untilpyyaml
is updated to support YAML 1.2.ISSUE TYPE
COMPONENT NAME
Every components that use pyyaml.
ADDITIONAL INFORMATION
In this reproducible example, my playbook applies a Kustomize file that deploys a Helm chart. In a production scenario, my Kustomize setup would include a Helm chart along with additional components. Why do I use Ansible this way instead of using the
helm
components? This is because I’m using the playbook only for the initial setup; after that, ArgoCD takes over and synchronizes changes to this Kustomize file.CRDs : https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus-operator-crds/charts/crds/templates
Linked PR on CRDs : prometheus-operator/prometheus-operator#4897
Playbook
Kustomize file
Error
The text was updated successfully, but these errors were encountered: