micqdf/TerraHome
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: micqdf:7434a65590c4a8c075cf88a638f182142d8d27e0
Branches Tags
micqdf:master micqdf:stage micqdf:destroy
micqdf:destroy/now
...
compare: micqdf:e4243c76678113e2fcdf752c62feebb25821fa09
Branches Tags
micqdf:master micqdf:stage micqdf:destroy
micqdf:destroy/now

2 Commits
7434a65590 ... e4243c7667

Author SHA1 Message Date
micqdf
e4243c7667 Merge pull request 'fix: keep DHCP enabled by default on template VM' (#129) from stage into master
Some checks failed
Terraform Apply / Terraform Apply (push) Failing after 1h50m42s
Details 
Reviewed-on: #129
 2026-03-08 22:03:17 +00:00
MichaelFisher1997
33bb0ffb17 fix: keep DHCP enabled by default on template VM
All checks were successful
Terraform Plan / Terraform Plan (push) Successful in 14s
Details 
The template machine can lose connectivity when rebuilt directly because it has no cloud-init network data during template maintenance. Restore DHCP as the default for the template itself while keeping cloud-init + networkd enabled so cloned VMs can still consume injected network settings.
 2026-03-08 20:12:03 +00:00
1 changed files with 1 additions and 1 deletions
Expand all files Collapse all files

2
nixos/template-base/configuration.nix
View File

@@ -10,7 +10,7 @@ in
./hardware-configuration.nix; ./hardware-configuration.nix;
networking.hostName = "k8s-base-template"; networking.hostName = "k8s-base-template";
networking.useDHCP = false; networking.useDHCP = lib.mkDefault true;
networking.useNetworkd = true; networking.useNetworkd = true;
networking.nameservers = [ "1.1.1.1" "8.8.8.8" ]; networking.nameservers = [ "1.1.1.1" "8.8.8.8" ];