Thanks a lot for all the information that you have added here.
There are two types of blueprint execution that are supported by K10.
- Hooks with blueprints.
- Data backup with blueprints.
Hooks with blueprints are executed before or action based on how it is configured in the policy.
Data operations with the profiles are not supported in this type of blueprint execution.
These execution hooks are designed in a way that these can be used to prepare your app/db before & after the backups. These can be some database commands to quiesce or unquiesce the database but not the data operations. These pre/post hooks cannot be used to capture output artifacts.
I see from the above policy screenshots that you are using the blueprints as hooks and that’s the reason the profile is not rendered.
You will have to remove this hooks from the policy and follow the next topic that I am going to explain.
Data backup with blueprints are used to override K10s snapshot workflow with the backup strategy that the blueprint specifies. This is what needs to be used to do a logical backup of your elasticsearch.
This workflow is invoked by a blueprint annotation to the workload(statefulset in this case) as specified in this documentation(https://docs.kasten.io/latest/kanister/elasticsearch/install_logical.html)
kubectl annotate statefulset elasticsearch-master kanister.kasten.io/blueprint='elasticsearch-blueprint' \
--namespace=elasticsearch
This will make sure that the profile can be rendered.
Please let me know if this works or if you have further questions.
