Add lifecycle policy for jetstream resources #303
Description
What motivated this proposal?
There are use cases where NATS Jetstream resources such as KeyValue is used for disaster recovery or similar.
In these cases it would make sense to be able to control how NACK handles for example deletions. It is not always the case that the wanted outcome is to delete the jetstream resource.
Crossplane is an excellent example, which uses managementPolicies that allow for orphaning managed resources.
What is the proposed change?
CRD:s are updated to have a NACK-specific section for how NACK should handle the resource. For starters, it could be a lifecycle policy that can be set to:
observe(simply check for existance and populate status accordingly)orphan(simply delete the CR without, orphaning the resource in NATS)delete(default behavior like now)
Who benefits from this change?
Anyone using NACK to handle Jetstream resources that are critical.
What alternatives have you evaluated?
None identified.