Unfortunately, after several tries, we were unable to restart the cluster due to a problem with the etcd leader election / data on the nodes (probably wrong manipulation from us).
We finally destroyed the cluster (we had to follow [1] because the cluster was in an unstable state and rancher refused to remove it)

I tried to fix it too but without success, so I guess we can go with this diff until we find a better solution

• Following this page to cleanup all the current resources on rancher-node-intership[0-2]: https://rancher.com/docs/rancher/v2.5/en/cluster-admin/cleaning-cluster-nodes/
• restart the nodes
• Delete the deployment-intership cluster in rancher
• Add the desire kubernetes version in terraform
• Apply
• launch the docker command to register the nodes in each node

thanks, I forgot to mention that

The error when we try to declare a resource in 1.22:

rebase

rebase

edit commit message

The command name called by postfix[1] seems to not match the command name declared in the webapp[2]

• rebase
• move the parameters after 'icinga_plugins'
• add an environment parameter

Here are the results of the queries.
You can directly paste the json in the search profiler to see the result.
(Be careful some are quite huge)

the file /var/lib/journalbeat/registry looks corrupted:
on worker10.euwest:

root@worker10:/var/lib/journalbeat# cat registry 
<?xml version="1.0" encoding="utf-8"?>
<GoalState xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="goalstate10.xsd">
  <Version>2012-11-30</Version>
  <Incarnation>1</Incarnation>
  <Machine>
    <ExpectedState>Started</ExpectedState>
    <StopRolesDeadlineHint>3

on worker09.euwest:

root@worker09:/var/lib/journalbeat# cat registry 
update_time: 2022-05-16T07:11:29.680690647Z
journal_entries:
- path: LOCAL_SYSTEM_JOURNAL
  cursor: s=1b5676c17e22450b80579b9caf065703;i=659f65c;b=97b0842367c749299a4a12ec839f1c3b;m=5b66c4ba4c0;t=5df1bbb86b72f;x=8e43c09dfc1a706e
  realtime_timestamp: 1652685086832431
  monotonic_timestamp: 6281059083456

LGTM, just 2 non-blocking questions inline

credentials created following https://docs.softwareheritage.org/sysadm/mirror-operations/onboard.html#how-to-create-the-objstorage-credentials

great, thanks

• rebase
• update according the review feedbacks

The cluster is declared and the node provisionning.

• fix the cloud-init / puppet concurrency after the vms startup
• remove the wrong vmid assigned to the new cluster nodes
• refresh the staging.tfstate file after applying the new configuration

Align worker0 and worker1 qemu arguments to match the real vms configuration

• fix wrong references to the elastic worker cluster
• rename nodes from rancher-node-internX to rancher-node-internshipX