ArgoCD Manifest error

[brimdor]

Similar issue to: #102
When running "make" for the first time, when it gets to the "system" portion, it fails.

system\bootstrap.yml

• name: Apply ArgoCD manifests
  kubernetes.core.k8s:
  resource_definition: "{{ argocd_manifests.stdout }}"
  apply: true
  server_side_apply:
  field_manager: argocd-controller

That task fails and gives the following error:
TASK [Apply ArgoCD manifests] ******************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible_collections.kubernetes.core.plugins.module_utils.k8s.exceptions.CoreException: Failed to load resource definition: 'str' object has no attribute 'setdefault'
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to load resource definition: 'str' object has no attribute 'setdefault'"}

To reproduce this error, start over from scratch, to replicate a first time build. You can do this using my reset script I put in a pull request along with other quality of life change suggestions. (#159)

Then run the usual process to build.

1. make tools
2. make configure (if needed)
3. make

Once it gets to the step described above, it will fail.

[fullstackjam]

You can retry run make, it will work

[brimdor]

Yes but that defeats the purpose of a single command build. You see this being performed in the video in the readme. That is not possible if the process has a break and then you have to run it again.

…

On Mon, Jul 29, 2024, 04:37 fullstackjam ***@***.***> wrote: You can retry run make, it will work — Reply to this email directly, view it on GitHub <#160 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJFVDZQHW7NXDDNLS4ASUTZOYEMLAVCNFSM6AAAAABHRDCT3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJVGQ2TSOBUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[fullstackjam]

• name: argo-cd
  version: 5.55.0
  works great

[fullstackjam]

interesting thing is when i use kubepary to install kubernetes: v1.30.3, make -C system works well, so i think question may be on k3s version