This message was deleted.
# k3sa
adamant-kite-43734
03/23/2026, 6:09 PMThis message was deleted.
c
creamy-pencil-82913
03/23/2026, 6:20 PMIf you wanted to rework that feature detection PR to allow disabling it via config, he might accept that? The rescanning thing shouldn’t be necessary, but the content events are just so inconsistent, its unfortunate that he’s kinda bet the farm on them.
a
average-appointment-24470
03/23/2026, 6:21 PMyeaa i know the whole spegel architecture has moved towards content events while they dont work either for ctr import and partially unusable for even upstream registry pulls.
average-appointment-24470
03/23/2026, 6:24 PMi can do that disabling content feature via config too. just wanna know if he rejects that solution, do we still have an option to cherrypick commit #645dae6 back to our fork?
c
creamy-pencil-82913
03/23/2026, 6:25 PMI dropped that from the k3s fork because he said he’d fixed content events… if he rejects it we can pull it into the k3s fork and figure out how to allow folks to enable it.
creamy-pencil-82913
03/23/2026, 6:25 PMbut we should at least try upstream first
a
average-appointment-24470
03/23/2026, 6:26 PMoks lemme look into that
average-appointment-24470
03/23/2026, 6:26 PMthanks
average-appointment-24470
03/23/2026, 8:07 PMaverage-appointment-24470
03/24/2026, 8:59 AMPhil wont be able to review this any soon ):)
c
clever-house-68727
03/30/2026, 5:35 PMHi, can you pull this PR in k3s spegel fork pls?
🙏 1
clever-house-68727
03/30/2026, 5:36 PM@creamy-pencil-82913 @average-appointment-24470 ^
a
average-appointment-24470
04/06/2026, 5:53 PM@creamy-pencil-82913 whats the next step here? lets pull this into our fork?
🙏 1
2 Views