Helm documentation states the following:
-1) (k8s) metadata.name is restricted to a maximum length of 63 characters because of limitations to the DNS system
-2) For that reasons, release names are (DNS labels that are) limited to 53 characters

Statement 1) is not correct.
k8s does not impose a max length of 63 characters on resource names.
The actual max length for a resource name is 253 c

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.

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

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

The buildkit (client) and buildkitd (builder daemon) can both be used with faasd or k3s hosts for building images without installing Docker onto the machine.

There is a tar that can be downloaded like we do with inletsctl, however, we need to make sure we extract both binaries. I'm fairly sure that this will "just work"

See more:

https://github.com/moby/buildkit/releases

Is your feature request related to a problem? Please describe.
When working with big images, okteto up times out often, specially if the image is pretty large and not pulled. It would be useful to be able to specify a bigger timeout directly in the manifest, instead of setting an env var.

First reported on Slack (https://kubernetes.slack.com/archives/C9D3TSUG4/p1550784319000900), it looks like if https://github.com/helm/monocular/blob/v1.2.0/cmd/chart-repo/utils.go#L100 comes back with an empty list (if there are no entries in the index.yaml, or all charts are deprecated), then https://github.com/helm/monocular/blob/v1.2.0/cmd/chart-repo/utils.go#L260 results in a panic as it tries

The TOC on the right hand side of https://toolkit.fluxcd.io/guides/helm-operator-migration/ is very crowded, let's add a mini-TOC at the top of the document to provide links to:

• discussion of breaking changes
• api spec changes
• migration strategy
• FAQ