-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: accumulating resources #19
Comments
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: Attempting installation with kustomize: sudo microk8s kubectl create namespace jitsi |
Oh! Now I see that there is a typo in the docu. The deployment file is I think this causes the problem. Just rename your I will update the documentation. Please let me know if this works for you. |
I updated the file name and kustomization.yaml
|
Then please take out the patchesStrategicMerge resoruce and test if this did work. |
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. |
ok, then I am no longer convinced that microk8s fully support kustomize. The error messages are also not helpful. |
Since I also do not know how to continue here, we have gone back to working with Kompose. |
Same issue here. I am on a bare metal cluster so i dont think it is because of microk8s. |
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. |
@rsoika i get exactly the same error message |
We get more or less the same issue, |
Just to sort things out: if you remove the resources and patches in your kustzomiz file like the following one. Is it working?
|
I have tried the helm install. Helm install is working. |
Still same issues when resources and patches are removed..
|
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. |
I am running v1.22.4 in aks |
Running 1.21.7 in aks.
We managed to use a workaround by downloading all the base files locally and not use the base feature. We have a plan to test this with a clean microk8s environment.
…________________________________
From: Jose Olivera ***@***.***>
Sent: Wednesday, February 23, 2022 1:10:26 PM
To: jitsi-contrib/jitsi-kubernetes ***@***.***>
Cc: Tim Nilimaa-Svärd ***@***.***>; Comment ***@***.***>
Subject: Re: [jitsi-contrib/jitsi-kubernetes] error: accumulating resources (Issue #19)
I am running v1.22.4
—
Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABN27S4DDKT42J5BUN6HIIDU4TFDFANCNFSM5NX323SA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***>
|
same problem, k3s v1.22.7 |
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:
I can go ahead and make a PR for this. |
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. |
Please give us some feedback if this solves your problem. Solution: replace in your
with
|
I went through the steps to deploy Jitsi on my microk8s cluster with kustomize and recieve following error:
error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize': yaml: line 218: mapping values are not allowed in this context': evalsymlink failure on '/tmp/kustomize-2873540753/tree/main/doc/kustomize' : lstat /tmp/kustomize-2873540753/tree: no such file or directory
What have I done wrong?
The plan is to run jitsi on a internal server and access the Service with the IP, without exposing anything to the internet, so a https certificate by letsencrypt is not required or relevant for us.
I enabled the Ingress microk8s addon and created the .yaml files like this:
010-deployment.yaml
041-ingress.yaml
kustomization.yaml
Thank you for your help!
The text was updated successfully, but these errors were encountered: