You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, imports & exports between accounts require the generation of activation tokens and then embedding these within the account resource of both importer and exporter.
I propose a new CRD NatsRoutingRule, that specifies:
Source Account
Source Topic(s)
Target Account
Target Topic / Subject Remapping
I assume that afterwards the Account JWTs for source and target need to be regenerated.
I would like to not touch the Kubernetes Objects of the respective accounts to dynamically add/remove exports.
The text was updated successfully, but these errors were encountered:
Currently, imports & exports between accounts require the generation of activation tokens and then embedding these within the account resource of both importer and exporter.
I propose a new CRD
NatsRoutingRule
, that specifies:I assume that afterwards the Account JWTs for source and target need to be regenerated.
I would like to not touch the Kubernetes Objects of the respective accounts to dynamically add/remove exports.
The text was updated successfully, but these errors were encountered: