Is there a recommended layout for multiple clusters sharing config? #152

Activity

1. clementnuss commented on Sep 23, 2026

   

   clementnuss

   on Sep 23, 2026

   Contributor

   More actions

   1.1 reusing the same 'config' folder for multiple clusters: yes, that's actually what we do.
   1.2 yes, patchesDir is resolved relative to the config file directory:

   	configFileDir := filepath.Dir(absPath)
   
   	// Set default patchesDir if not specified
   	if config.PatchesDir == "" {
   		config.PatchesDir = configFileDir
   	} else if !filepath.IsAbs(config.PatchesDir) {
   		config.PatchesDir = filepath.Join(configFileDir, config.PatchesDir)
   	}

   2. for now this is the intended way. but there are discussions/ideas in Feature request: allow additional roles for a node #44 to have a classes: [] field on the node object, which would let topf gather class-specific patches in a folder of the same name. not sure we go that route yet though
   3. this is actually a nice idea, which might (help) solve Feature request: allow additional roles for a node #44. we'll discuss it with @sebastian-stephan !

   FYI: the way we organize our talos config is as follows:

   • we have a talos/config repository, containing the shared config for all clusters
   • we run topf in a GitLab pipeline. the 'init' script that runs topf starts by cloning out the config repository.
   • currently we store the repo name and the revision in topf.yaml/data.repository..., and the init script consumes those values to clone the repo. there would also be an idea for a config provider, but that goes against topf's goal to stay minimal. configProvider? #94
2. postfinance

   locked and limited conversation to collaborators on Sep 23, 2026
3. clementnuss

   converted this issue into a discussion #157 on Sep 23, 2026