JenTing comments

Results 212 comments of


                                            JenTing

velero needlessly requires sh in kubectl image

Related to #571

Warning messages on active indexes

Please help file this issue to velero repo, this repo is dedicated for helm chart, thanks.

build(deps): bump github.com/vmware-tanzu/velero from 1.15.2 to 1.16.0

@dependabot rebase

Extend helm values with HostAliases

Is this configuration support in the both Deployment and DaemonSet?

Fail to install velero helm chart 3.2.0. Getting error - job failed: BackoffLimitExceeded

> This has been working until Feb 19th, 2024. We did not touch the release recently. Perhaps the problem is the kubectl image isn't available.

Fail to install velero helm chart 3.2.0. Getting error - job failed: BackoffLimitExceeded

Related issue #559, closing it.

helm upgrade for velero failing error Error: UPGRADE FAILED: post-upgrade hooks failed: 1 error occurred: * job failed: BackoffLimitExceeded

Related issue #559, closing it.

backup PV error

It looks like it's Velero issue. Could you please file this issue to [vmware-tanze/velero](https://github.com/vmware-tanzu/velero/issues)?

Upgrade to 4.1.5 and higher failed with "SchemaError(io.velero.v1.Restore.spec.hooks.resources.postHooks.init.initContainers): array should have exactly one sub-item"

Have you try the above solution?

Whats the impact of removing the auto mount of access token for velero service accounts

@mackmittalwk I remember that Kubernetes supports auto mount the service account token. The purpose is that the Pod is able to authenticate to the kube-apiserver. I think we could disable...