Skip to content

Feature: Statefile per nodepool #1895

@bernardhalas

Description

@bernardhalas

Motivation

Internally, Claudie uses OpenTofu for provisioning cloud infra. Currently, it stores one statefile per cluster.
This is a problem for scenarios, where there's an OpenTofu template upgrade that needs to be synced with OpenTofu provider upgrade. The nature of the problem lies in the fact, that template upgrades are rolled-out via a rolling update on a nodepool basis.

This means, if there's a template update, that concerns an existing nodepool, Claudie creates a new nodepool with the new template version before deleting the original nodepool created by the older template version. This creates a conflict as in one OpenTofu statefile can be just one tofu provider version.

Description

Break up statefiles into one per nodepool.

Exit criteria

  • Claudie creates one statefile per nodepool
  • OpenTofu templates can pin tofu provider version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions