ate-operator: Make it easy to install and manage (multiple) substrates #64

Activity

1. Michael Taufen (mtaufen)

   added the

   Feature

   issue type on May 22, 2026
2. Michael Taufen (mtaufen)

   added

   area/apiUser-facing API changesUser-facing API changes

   kind/featureAn enhancement / feature request or implementationAn enhancement / feature request or implementation

   on May 22, 2026
3. Tim Hockin (thockin)

   added

   prio/P1Important but not criticalImportant but not critical

   on May 31, 2026
4. thockin commented on May 31, 2026

   

   Tim Hockin (thockin)

   on May 31, 2026

   Collaborator

   More actions

   The problem with "apply a CR to your namespace" is that substrates CAN span namespaces, right? #18
5. mtaufen commented on Jun 1, 2026

   

   Michael Taufen (mtaufen)

   on Jun 1, 2026 via email

   CollaboratorAuthor

   More actions

   If someone is deploying a substrate across namespaces, do we assume they own the full set of namespaces it spans?

   …

   On Sun, May 31, 2026, 3:39 PM Tim Hockin ***@***.***> wrote: *thockin* left a comment (agent-substrate/substrate#64) <#64 (comment)> The problem with "apply a CR to your namespace" is that substrates CAN span namespaces, right? #18 <#18> — Reply to this email directly, view it on GitHub <#64?email_source=notifications&email_token=AAG4TQKXTEBE525OZAT4ZHT45SYBPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DENZVGQY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4588427541>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG4TQK6JLKPUUFQFONTYIT45SYBPAVCNFSM6AAAAACZJVFEDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOBYGQZDONJUGE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAG4TQLRZLLIMCV35AGXNEL45SYBPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DENZVGQY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AAG4TQJRTIYGY5D6CZYUCFT45SYBPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DENZVGQY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>
6. mtaufen commented on Jun 1, 2026

   

   Michael Taufen (mtaufen)

   on Jun 1, 2026 via email

   CollaboratorAuthor

   More actions

   We can also make it easy in one NS first, then figure out how to best handle multi.

   …

   On Mon, Jun 1, 2026, 2:39 PM Michael Taufen ***@***.***> wrote: If someone is deploying a substrate across namespaces, do we assume they own the full set of namespaces it spans? On Sun, May 31, 2026, 3:39 PM Tim Hockin ***@***.***> wrote: > *thockin* left a comment (agent-substrate/substrate#64) > <#64 (comment)> > > The problem with "apply a CR to your namespace" is that substrates CAN > span namespaces, right? #18 > <#18> > > — > Reply to this email directly, view it on GitHub > <#64?email_source=notifications&email_token=AAG4TQKXTEBE525OZAT4ZHT45SYBPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DENZVGQY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4588427541>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAG4TQK6JLKPUUFQFONTYIT45SYBPAVCNFSM6AAAAACZJVFEDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOBYGQZDONJUGE> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/AAG4TQLRZLLIMCV35AGXNEL45SYBPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DENZVGQY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> > and Android > <https://github.com/notifications/mobile/android/AAG4TQJRTIYGY5D6CZYUCFT45SYBPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DENZVGQY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. > Download it today! > You are receiving this because you authored the thread.Message ID: > ***@***.***> >