Kuberenets cluster recipe not happy
-
@olivierlambert I deleted all templates from XOA by going to "Hub" > "Templates" and using the trash icon to remove them. However it still appears that it uses debian 9. I could try to remove all templates from the system via the windows xcp-ng client. However it may be of importance to know that i have never used the debian 9 template before. While using this recipe was the first time i saw it.
I remember trying the k8s recipe about a year ago, maybe that has tainted my setup in some way?
-
How do you check it's using Debian 9 template exactly?
-
@olivierlambert Under the VM page "Advanced" > "Misc"
-
@mathiashedberg I've just checked the ones I built that started all of this... they are deb 9.
Peter.
-
Can you provide a screenshot?
Also, double checking inside the VM that's debian 9 with a
cat /etc/issue. Because the original template doesn't mean anything. -
@olivierlambert Ahh... it is 10 on the inside. 9 on the wrapper
-
You can create a Debian 10 VM using a Debian 9 template, it doesn't matter (both are HVM guests, same config).
The current VM was probably made while Debian 10 template wasn't there yet.
-
So after some more testing it seems the template mapping is wrong again. My k8s VMs started with 500MB, and when i looked at the bash history, i saw that yet again, the k8s VMs were based on an existing VM running on the system. The ram was set to 500MB because thats what the base VM ram settings were. This is the same issue as earlier on.
-
Are you sure you removed the templates?
-
So this new VM for k8s seems to be based on an existing VM, which itself is based on the Debian 10 template (when it was created a long time ago)
-
@olivierlambert Ill remove them using the windows client
-
Our recipe is based on Debian available in XO Hub template.
-
In XO, you can search it in Templates view and remove it
-
@olivierlambert Yes i removed it from the Hub > Templates view. It should be noted that i take regular backups of the VMs created with this debian 10 template, so i think it is using them
Backups are done with the XCP-NG center: 'Pool' > 'VM Snapshot Schedule' setting
-
Please do NOT use XCP-ng Center "snapshot schedule" feature please
-
@olivierlambert For a homelab setup this is currently the only "free" solution to snapshotting that i know of (other than file system based like ZFS).
Going from "free" to 77USD a month is quite a jump imo.
-
It's a bit off topic but:
- Remember, snapshot is not backup
- You can use XO from the sources to have all XO source code without feature restrictions (but XO hub/recipe is XOA because it's a service connected on xen-orchestra.com where we host the machines).
Anyway, let's try to find the original problem
-
@mathiashedberg said in Kuberenets cluster recipe not happy:
@olivierlambert For a homelab setup this is currently the only "free" solution to snapshotting that i know of (other than file system based like ZFS).
Going from "free" to 77USD a month is quite a jump imo.
Xen Orchestra is free and open source. You can follow the build from source instructions or use a script like the one posted to my github
-
@olivierlambert
The snapshot functionality is still quite tempting to use, as I have not had any issues with it before now. I'll admit I'm not too up to date on what features are recommended or not when it comes to XCP-NG.@DustinB I think its great that we have such useful software that is free and open source. If my comment came off as negative I apologize, that was not my intention.
Moving forward I would assume that removing all my snapshots would remedy the issue. However I'm not too sure on how keen I am on doing that right at this moment with my current setup, maybe on a different test lab.
-
@mathiashedberg the snaphots might be indeed the problem.
When looking for the template, the recipe looks for a VM with
xo:resource:xva:id=<template uuid>in itsother-config, a snapshot of the template VM would probably have this field se and it should not.Can you check if it's the case? and if the
is-templatefield istrue.
