CrashLoopBackOff
state on OCP IBM cloud. This issue has now been fixed.cleanupOnFailure
flag in restore was previously causing an issue where an infinite number of cleanup pods were being created. This issue is now fixed.cleanupOnFailure
flag in restore CR, then sometimes the cleanup job is created infinitely. We are working on this issue with priority and will create patch as soon as this is fixed.cleanupOnFailure
flag in restore CR, then sometimes the cleanup job is created infinitely. We are working on this issue with priority and will create patch as soon as this is fixed.RetainHelmApps
flag is provided for namespace/multi-namespace backups, which can be specified in backup plans and subsequently propagated to associated backups. If this flag is specified as true, TVK will backup helm applications using helm way during namespace-level backup. In other words, after the restore of this kind of backup, the user will find the helm application exactly as it is supposed to be. To use this feature, it is recommended for the user to create a new namespace/multi-namespace backupplan.cleanupOnFailure
flag in restore CR, then sometimes the cleanup job is created infinitely. We are working on this issue with priority and will create patch as soon as this is fixed.Error: INSTALLATION FAILED: failed pre-install: warning: Hook pre-install k8s-triliovault-operator/templates/TVMCustomResource.yaml failed:
TrilioVaultManager.triliovault.trilio.io
"triliovault-manager" is invalid: spec.tvkInstanceName: Invalid value: "null": spec.tvkInstanceName in body must be of type string: "null"
Now, as a part of TVM CR, you can mention the tvkInstanceName in the specification. Alternatively, in the case of OCP, you can edit the k8s-triliovault-config configmap to provide the instance name. This clears the error and enables users to proceed with installation.triliovault-dex
secret.v2.0.4
version will be automatically upgraded to v2.0.5
via OLM if the subscription is set to automatic. If not, manually approve the subscription upgrade.v1.1.1 or v2.0.0
to v2.0.5
- either incrementally upgrade to the next version up to v2.0.3
or uninstall the current operator and reinstall the 2.0.4 operator from OperatorHub.v2.0.2
version will be automatically upgraded to v2.0.4
via OLM if the subscription is set to automatic. If not, manually approve the subscription upgrade.v1.1.1 or v2.0.0
to v2.0.4
- either incrementally upgrade to the next version up to v2.0.3
or uninstall the current operator and reinstall the 2.0.4 operator from OperatorHub.ClusterIPs
for the service
resource that is auto-populated from the clusterIP
field. Trilio wipes out the clusterIP
field from a service resource before a restore, but the ClusterIPs
field cannot be non-empty with the clusterIP
field. As a result, the restore validation fails. Trilio will fix this issue in a subsequent release, but until then restore transformations can be used to workaround this issue. A video explaining the transform can be found here\v2.0.2
version will be automatically upgraded to v2.0.3
via OLM if the subscription is set to automatic. If not, manually approve the subscription upgrade.v1.1.1 or v2.0.0
to v2.0.3
- either incrementally upgrade to the next version up to v2.0.3
or uninstall the current operator and reinstall the 2.0.3 operator from OperatorHub.ClusterIPs
for the service
resource that is auto-populated from the clusterIP
field. Trilio wipes out the clusterIP
field from a service resource before a restore, but the ClusterIPs
field cannot be non-empty with the clusterIP
field. As a result, the restore validation fails. Trilio will fix this issue in a subsequent release, but until then restore transformations can be used to workaround this issue. A video explaining the transform can be found here\v2.0.1
version will be automatically upgraded to v2.0.2
via OLM if the subscription is set to automatic. If not, manually approve the subscription upgrade.v1.1.1 or v2.0.0
to v2.0.2
- either incrementally upgrade to the next version up till to 2.0.2 or uninstall the current operator and reinstall the 2.0.2 operator from OperatorHub.v2.0.0
version will not be automatically upgraded to v2.0.1
if the auto publish is enabled as the images for 2.0.0 were being served from the namespace channel. The channel will have to be changed back to cluster to receive the update. A video has been provided on the Upgrade page that demonstrates the processCustomResourceWebhookConversion
feature gate on the cluster