NodePortassigned to service
k8s-triliovault-ingress-gatewayis added in the firewall rules Protocols and Ports.
kubectl apply -f <backup_target.yaml>is not successful and the resource goes into
Unavailablecould be not having enough permissions or lack of network connectivity. Target resource creation launches a validation pod to check if TrilioVault can connect and write to the Target. TrilioVault then cleans the pod after the validation process completes, which clears any logs that the validation pod has. Users should repeat the same operation and actively check the logs on the validation pods.
<backupname>-snapshot: TrilioVault leverages CSI snapshot functionality to take PV snapshots. If the backup fails in this step user should try a manual snapshot of the PV to make sure all required drivers are present, and that this operation works without TrilioVault.
<backupname>-upload: In this phase, TrilioVault uploads metadata and data to the Target. If the backup fails in this phase, we need to look into the following logs for error.
Internal error occurred: failedor
service "k8s-triliovault-webhook-service" not found
ClusterServiceVersion(CSV)Users can either edit the Operator CSV YAML directly from within the OCP console or can patch the pods based on the snippets provided below.