Output of helm version:
version.BuildInfo{Version:"v3.8.1", GitCommit:"5cb9af4b1b271d11d7a97a71df3ac337dd94ad37", GitTreeState:"clean", GoVersion:"go1.17.8"}

If HELM_DATA_HOME contains spaces, like `/Users/My Name/Library/hel

So much emphasis on the buttons is not needed.

Expected Behaviour

Change the default cron spec in --etcd-snapshot-schedule-cron (default: "0 */12 * * *"):

--k3s-extra-args '--etcd-snapshot-schedule-cron * * * * *'

Describe the bug

When calling vela provider add twice or more times, the error message is generic and only says Error: failed to authenticate Terraform cloud provider terraform-<provider>. The error should be passed back to the CLI. In the case you run it more than once, the err on https://github.com/kubevela/kubevela/blob/

In #2649, all our dependencies except this module in the Azure related end-to-end tests were updated, as it contains a breaking change.

tfinstall has been removed and needs to be replaced with https://github.com/hashicorp/hc-install. We call it exactly one time in [azure_test.go](https://github.com/

Description

Currently there is no icon for DOCR:

Location

• Browser
• CLI
• API

Steps to reproduce

1. Provision a registry to DO or link one through the CLI
2. View connected docker registries from the "Integrations" tab

Additional Details

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

Expected Behaviour

When using K8s 1.22 and newer, use the new namespace for ingress, for older use the deprecated API (apiVersion: extensions/v1beta1)

Several apps gener

Is your feature request related to a problem?

Mutating webhooks often use label selectors to determine which resources to process. Since vcluster mutates all the labels on synced resources, this can prevent webhooks in the physical cluster from being able to mutate the physical resources.

In particular we've encountered this issue for synced pods.

Which solution do you suggest?