Tiger Kaovilai

icon indicating a website link kaovilai.pw

icon company Red Hat icon location Raleigh, NC, USA; Bangkok, Thailand icon location A gopher in the Kubernetes space. I contribute to @project-velero to protect @openshift & @kubernetes workloads.

Results 652 comments of Tiger Kaovilai

Increase ensure restic repository timeout

For 1.10+ (and `main`) I would consider making the timeout configurable if we couldn't find root cause before merging this PR.

Velero backup v1 custom resource failed since it's trying fetch v1beta1 CR

``` time="2022-09-28T14:24:58Z" level=info msg="Found associated CRD mtxengines.matrixx.com to add to backup" backup=velero-ppdm/mtx-prod-e1-2022-09-28-17-22-37-mtx-prod-e1 logSource="pkg/backup/backup.go:480" time="2022-09-28T14:24:58Z" level=info msg="Backing up item" backup=velero-ppdm/mtx-prod-e1-2022-09-28-17-22-37-mtx-prod-e1 logSource="pkg/backup/item_backupper.go:121" name=mtxengines.matrixx.com namespace= resource=customresourcedefinitions. time="2022-09-28T14:24:58Z" level=info msg="Executing custom action" backup=velero-ppdm/mtx-prod-e1-2022-09-28-17-22-37-mtx-prod-e1 logSource="pkg/backup/item_backupper.go:327"...

Velero backup v1 custom resource failed since it's trying fetch v1beta1 CR

`CustomResourceDefinition mtxengines.matrixx.com appears to be v1beta1, fetching the v1beta version`

Velero backup v1 custom resource failed since it's trying fetch v1beta1 CR

prior answers https://github.com/vmware-tanzu/velero/issues/4080#issuecomment-1047658192

Velero backup v1 custom resource failed since it's trying fetch v1beta1 CR

Regarding usage of v1beta1 CRD of kopfpeerings.zalando.org, I would recommend transitioning to it's successor project and follow instruction at https://github.com/nolar/kopf/pull/644

error `413 request entity too large` while pushing an image

I am hitting this issue in a repeatable GitHub actions. Feel free to try there.

error `413 request entity too large` while pushing an image

@z4ce please check https://github.com/richstokes/k8s-fah/actions/runs/3157318749/jobs/5138045405#step:11:263

Circular dependency with testify

Just a go.sum eyesore that's all. For some reason golang don't prevent module circular dependency but does at the package level.

OADP-772: User wants to know what to expect in each `Update channel` of OADP Operator

/lgtm

OADP-772: User wants to know what to expect in each `Update channel` of OADP Operator

Any reason this doc is 4.11+ only?