Replies: 1 comment 2 replies
-
We actually have an operator that I think does exactly this (or something very similar). Check this out: https://github.com/Apicurio/apicurio-registry-content-sync-operator Perhaps that can be leveraged to accomplish what you suggest? @jsenko thoughts? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With in-memory storage option, when registry instance is drained or restarted the state with all artifacts will be lost.
The proposed optimization: let's define a CRD for the artifact that will be consumed by apicurio operator.
When a new instance of the registry is loaded, it will initialize its state from the Kubernetes resources.
I would happy to hear your opinion on that
Beta Was this translation helpful? Give feedback.
All reactions