- Aug 25, 2023
-
-
Vincent Sellier authored
Related to sysadm-environment#4730
-
Vincent Sellier authored
Related to sysadm-environment#4730
-
- Aug 24, 2023
-
-
Vincent Sellier authored
Related to sysadm-environment#4730
-
- Aug 18, 2023
-
-
Vincent Sellier authored
Related to sysadm-environment#4999
-
- Aug 17, 2023
-
-
Vincent Sellier authored
It's necessary to use a 1.25+ compatible version Related to sysadm-environment#4999
-
Vincent Sellier authored
Related to sysadm-environment#4999
-
Vincent Sellier authored
Related to sysadm-environment#4999
-
- Mar 22, 2023
-
-
Antoine R. Dumont authored
Refs. sysadm-environment#4816
-
- Jan 10, 2023
-
-
Vincent Sellier authored
Related to CPUThrottlingHigh
-
- Jan 06, 2023
-
-
Antoine R. Dumont authored
That matches the default terraform key too.
-
Antoine R. Dumont authored
-
- Dec 26, 2022
-
-
Vincent Sellier authored
rancher/monitoring: configure node-exporter to store node name instead of the ip for the instance label Rancher use an modified version of the prometheus-stack helm chart so the configuration is a little different than the official helm chart Related to infra/sysadm-environment#4705
-
Vincent Sellier authored
Related to infra/sysadm-environment#4695
-
- Dec 19, 2022
-
-
Vincent Sellier authored
Related to infra/sysadm-environment#4385
-
- Dec 09, 2022
-
-
Vincent Sellier authored
-
- Nov 30, 2022
-
-
Vincent Sellier authored
Related to infra/sysadm-environment#4688
-
Vincent Sellier authored
If not, the pods are abruptly killed. Related to infra/sysadm-environment#4688
-
- Nov 15, 2022
-
-
Vincent Sellier authored
and reorder the prometheus configuration to make terraform happy Related to infra/sysadm-environment#4385 and infra/sysadm-environment#4604
-
- Nov 14, 2022
-
-
Vincent Sellier authored
Related to infra/sysadm-environment#4665
-
- Nov 09, 2022
-
-
Vincent Sellier authored
Related to infra/sysadm-environment#4664
-
- Nov 04, 2022
-
-
Vincent Sellier authored
-
- Sep 28, 2022
-
-
Vincent Sellier authored
Related to T4461
-
- Sep 09, 2022
-
-
Nicolas Dandrimont authored
-
- Sep 08, 2022
-
-
Vincent Sellier authored
-
- Sep 06, 2022
-
-
Vincent Sellier authored
-
- Aug 26, 2022
-
-
Antoine R. Dumont authored
-
- Jul 28, 2022
-
-
Antoine R. Dumont authored
Related to T4135
-
Antoine R. Dumont authored
Use with `terraform output $CLUSTER_NAME-{config-summary|register-command}`: - config-summary: config yaml to merge within ~/.kube/config to access cluster info - register-command: docker command executed to register node to the cluster Related to T4135
-
Antoine R. Dumont authored
Related to T4135
-
Antoine R. Dumont authored
Related to T4135
-
- Jul 27, 2022
-
-
Antoine R. Dumont authored
This should help maintaining references up-to-date. Also, when destroying and spawning back an identical vm, we shall then have a most recent image and faster provisioning build. Related to T4410
-
- Jul 21, 2022
-
-
Antoine R. Dumont authored
Related to T4405
-
- Jul 07, 2022
-
-
Antoine R. Dumont authored
Related to T4385
-
- Mar 30, 2022
-
-
Vincent Sellier authored
Related to T4045
-
- Mar 29, 2022
-
-
Vincent Sellier authored
-
- Feb 01, 2022
-
-
Antoine R. Dumont authored
-
- Jan 25, 2022
-
-
Antoine R. Dumont authored
``` $ terraform apply module.dali.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/144] module.bojimans.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/127] module.rp1.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/115] module.bardo.proxmox_vm_qemu.node: Refreshing state... [id=hypervisor3/qemu/124] Note: Objects have changed outside of Terraform Terraform detected the following changes made outside of Terraform since the last "terraform apply": # module.bojimans.proxmox_vm_qemu.node has changed ~ resource "proxmox_vm_qemu" "node" { ~ balloon = 2048 -> 0 ~ cpu = "kvm64" -> "host" - desc = "Inventory server (netbox)" -> null id = "branly/qemu/127" name = "bojimans" # (39 unchanged attributes hidden) ~ disk { + discard = "on" # (18 unchanged attributes hidden) } # (1 unchanged block hidden) } Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these changes. ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place ... Enter a value: yes module.bojimans.proxmox_vm_qemu.node: Modifying... [id=branly/qemu/127] module.bojimans.proxmox_vm_qemu.node: Still modifying... [id=branly/qemu/127, 10s elapsed] module.bojimans.proxmox_vm_qemu.node: Still modifying... [id=branly/qemu/127, 20s elapsed] module.bojimans.proxmox_vm_qemu.node: Still modifying... [id=branly/qemu/127, 30s elapsed] module.bojimans.proxmox_vm_qemu.node: Modifications complete after 30s [id=branly/qemu/127] Apply complete! Resources: 0 added, 1 changed, 0 destroyed. Outputs: bojimans_summary = <<EOT hostname: bojimans fqdn: bojimans.internal.admin.swh.network network: ip=192.168.50.60/24,gw=192.168.50.1 macaddrs=EE:ED:A6:A0:78:9F vmid: 127 ... ``` Related to T3873
-
- Jan 14, 2022
-
-
Vincent Sellier authored
Related to T3817
-
- Jan 12, 2022
-
-
Antoine R. Dumont authored
Adding an extra disk to install the dbs' data on that mount point. Related to T3833
-
- Dec 15, 2021
-
-
Vincent Sellier authored
Using the null value to use the default proxmox value is not working. The `host` value is restored on the state after a refresh if it's not forced to kvm64. Related to T3795
-