Output of helm version:

Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"d

Describe the bug

In the official docs, the page for Helm notes that variables can be substituted using the $ character, but do not specify how to escape them. The user should not have to dig through the source code for this information. If this is not a supported feature, then the docs should state this very clearly.

To Reproduce

See https://argo-cd.readthedocs.io/en/stable/user-g

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

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

When an application created and component has something wrong that failed to apply, our application status doesn't report the apply error in status.services.[component], but only some info in condition. We should record the apply error in the services field.

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

Using #1671 as an example we could add unit tests for the flux create secret git/helm/tls --export commands and validate the YAML output against golden file.

Is your feature request related to a problem? Please describe.
I want to strictly run my Okteto pods in special worker nodes e.g. GPU enabled.

Describe the solution you'd like
Add nodeSelector and affinity options to Okteto manifest that maps to nodeSelector and affinity in Kubernetes manifest.

Describe alternatives you've considered
2 alternatives to solve this proble