error: accumulating resources about jitsi-kubernetes HOT 21 OPEN

Ok so the deal is that kustomize git urls are a complete mess and there's a whole chaos of issues and PRs about it, with this being the latest: kubernetes-sigs/kustomize#4454

What worked for me was removing https:// and /tree/main from the url, so you have:

namespace: jitsi
bases:
- github.com/jitsi-contrib/jitsi-kubernetes/doc/kustomize
...

I can go ahead and make a PR for this.

from jitsi-kubernetes.

Please give us some feedback if this solves your problem.

Solution:

replace in your kustomization.yaml file the line

- https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize

with

- github.com/jitsi-contrib/jitsi-kubernetes/doc/kustomize

from jitsi-kubernetes.

I attempted a fresh microk8s installation on my local computer and ended up with the same Error, mentioning line 220.

Here are all commands i executed:
Installing Microk8s and dashboard:
sudo snap install microk8s --classic
sudo ufw allow in on cni0 && sudo ufw allow out on cni0
sudo ufw default allow routed
sudo microk8s enable dns dashboard storage
sudo microk8s status
sudo microk8s kubectl get all --all-namespaces
token=$(microk8s kubectl -n kube-system get secret | grep default-token | cut -d " " -f1)
sudo microk8s microk8s kubectl -n kube-system describe secret $token

Attempting installation with kustomize:
mkdir my-jitsi
cd my-jitsi
vim kustomization.yaml
vim 010-deployment.yaml
-> I took the ingress file out
-> I set the PUBLIC_URL to my IP

sudo microk8s kubectl create namespace jitsi
sudo microk8s kubectl create secret generic jitsi-config -n jitsi --from-literal=JICOFO_COMPONENT_SECRET=start --from-literal=JICOFO_AUTH_PASSWORD=start --from-literal=JVB_AUTH_PASSWORD=start
sudo microk8s kubectl apply -k ./my-jitsi

from jitsi-kubernetes.

Oh! Now I see that there is a typo in the docu.

The deployment file is 030-deployment.yaml and not '010-.....'

I think this causes the problem. Just rename your 010-deployment.yaml into 030-deployment.yaml This should do the trick.

I will update the documentation. Please let me know if this works for you.

from jitsi-kubernetes.

I updated the file name and kustomization.yaml
Sadly the issue remains.

error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize': yaml: line 225: mapping values are not allowed in this context': evalsymlink failure on '/tmp/kustomize-1066009744/tree/main/doc/kustomize' : lstat /tmp/kustomize-1066009744/tree: no such file or directory

from jitsi-kubernetes.

Then please take out the patchesStrategicMerge resoruce and test if this did work.
If yes, than something in your 030-deployment.yaml is incorrect.

from jitsi-kubernetes.

The attempt with just the kustomization.yaml, without the resources and patchesStrategicMerge files did not work either, same error.

I appreciate your support!

Another idea is, the containerization of snap could cause issues accessing the tmp files.

from jitsi-kubernetes.

ok, then I am no longer convinced that microk8s fully support kustomize. The error messages are also not helpful.

from jitsi-kubernetes.

Since I also do not know how to continue here, we have gone back to working with Kompose.

from jitsi-kubernetes.

Same issue here. I am on a bare metal cluster so i dont think it is because of microk8s.

from jitsi-kubernetes.

But kompose and kustomize are different concepts. I can't believe that you get the same error message. If so, it sounds to me that you have a different problem.

from jitsi-kubernetes.

@rsoika i get exactly the same error message

from jitsi-kubernetes.

We get more or less the same issue,
% kubectl apply -k ./my-jitsi error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize': yaml: line 237: mapping values are not allowed in this context': evalsymlink failure on '/private/var/folders/q_/yfghdtd147xf71g9wf9fn66h0000gn/T/kustomize-954443534/tree/main/doc/kustomize' : lstat /private/var/folders/q_/yfghdtd147xf71g9wf9fn66h0000gn/T/kustomize-954443534/tree: no such file or directory

from jitsi-kubernetes.

Just to sort things out: if you remove the resources and patches in your kustzomiz file like the following one. Is it working?

namespace: jitsi
bases:
- https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize

#resources:
#- 041-ingress.yaml

#patchesStrategicMerge:
#- 030-deployment.yaml

from jitsi-kubernetes.

I have tried the helm install. Helm install is working.

from jitsi-kubernetes.

Still same issues when resources and patches are removed..

namespace: jitsi
bases:
- https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize

#resources:
#- 041-ingress.yaml

#patchesStrategicMerge:
#- 030-deployment.yaml

from jitsi-kubernetes.

Can someone narrow down the issue if this is related to the kubernetes environment/version? I am running in v1.21.6 and can not reproduce this kind of issue.

from jitsi-kubernetes.

I am running v1.22.4 in aks

from jitsi-kubernetes.

from jitsi-kubernetes.

same problem, k3s v1.22.7

from jitsi-kubernetes.

Yes you are totally right! There is in deed a wrong URL in the docu and I have overseen this all the time during this discussion.

from jitsi-kubernetes.