@ferrao Yes it is. At the end the task disappears unless there is an error / failure.

@ferrao open the VMs list (Home>VMs), click on "Filters" near the search bar, and then click "Save...", in the popup dialog enter a name for the filter and click "OK".

This should be enough to workaround the 2nd bug that happened at the end (that prevent to save the tag that is added to the clusters VMs)

@ferrao Thank you for the logs, with it I was able to reproduce the bug.

It's at the end of the recipe, when the tag associated with the k8s cluster is saved in the user's custom filters. This has no effect on the cluster creation, as this is done at the end when everything else is done.

To avoid this bug in future runs, you can save a custom filter from the search field in the VMs list.

About the first error you encounter, it's related to the template used to create the VM, which seems not available at the VM creation... I'm working on this to understand why.

@abreaux said in Kubernetes Recipe:

Is there any way to get the cloud-init used in the Hub Kubernetes recipe? Looking to customize the deployment using Terraform and I want to make sure I include all the same tasks.

What do you want to do actually? Do you want to "edit" a VM that has been deployed with the recipe (1), or do you want to deploy a new cluster that will copy the hub recipe (2)?

In case of (1), you can find the cloud-init content inside the VM itself: /var/lib/cloud/instance/cloud-config.txt

In the case of (2), the current version (5.105) of the k8s recipe is not really stable and is not intended to be used with Terraform. I can only recommend to find another solution (you can find some examples in the DevOps mega thread, like using Rancher).

In the next release of XOA, we have updated the Kubernetes recipe to use MicroK8s, which provides a light, open-source, scalable and production-ready Kubernetes distribution.

Release v1.5.2

The provider is now available on the Pulumi official Registry

https://www.pulumi.com/registry/packages/xenorchestra/

We added example for Yaml in the documentation.

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2

Hello,
If you want to discuss the Pulumi Provider in detail, let discuss here: https://xcp-ng.org/forum/topic/10592/pulumi-xen-orchestra-news

@nathanael-h said in DevOps Megathread: what you need and how we can help!:

Hello there, we released a new Pulumi Xen Orchestra provider last month ! It's worth noting that the work on this was started by some contributors from DESY, and that now we (Vates) commit to support and maintain it. This demonstrate the strength of joined work from both community and Vates on free and open source softwares

So what is offered is to declare your infrastructure as code, in Javascript or Typescript, Go, or Python (pick the one you prefer ) and to deploy, maintain, and update it.

https://github.com/vatesfr/pulumi-xenorchestra/

---

Release v1.5.0

The Pulumi Xen Orchestra provider is now available with Dotnet SDK!

• JavaScript/TypeScript: @vates/pulumi-xenorchestra
• Python: pulumi-xenorchestra
• Go: github.com/vatesfr/pulumi-xenorchestra/sdk
• .NET: Pulumi.Xenorchestra

What's Changed

• Feat: Add dotnet support
• Add docs for Dotnet SDK and unify examples

The Pulumi schema doesn't support u64 (or i64), so we convert to a float64, which should get us at least 2^52 bits of precision while minimizing the breaking change (int -> float) for our users.

List of properties to be updated from "integer" to "number"/float64:

Resources

• "xenorchestra:index/vm:Vm":
  • 🟡 inputs: "memoryMax" type changed from "integer" to "number"
  • 🟡 properties: "memoryMax" type changed from "integer" to "number"

Types

• 🟡 "xenorchestra:index/VmDisk:VmDisk": properties: "size" type changed from "integer" to "number"

How to migrate Golang stack code

Replace pulumi.Int(...) with pulumi.Float64(...)

Other SDKs do not seem to be affected by the changes.

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.0

---

Release v1.5.2

• The provider is now available on the Pulumi official Registry: https://www.pulumi.com/registry/packages/xenorchestra/
• Added example for Yaml

Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v1.5.2

---

What's next?

Upgrade the Pulumi SDK and others libraries to the latest version and provider Java sdk.

If you are using Pulumi Xen Orchestra, please share your experiences and needs with us

@wezke you are welcome. let us know if you find the explanation for the problem with the template

@wezke Hi, I have no problem running your terraform plan, maybe there is a problem with the template you are using? How did you create it?

There is no warning during the tf execution?