Liran BG

Nuctl would do the registration for you, it is preferably than do it manually because these scenario are not tested and I wouldnt recommend it. not to mention you lose...

imo github throttling against launching / restarting too fast. you can run nuclio dashboard with env `NUCLIO_TEMPLATES_GITHUB_ACCESS_TOKEN` and your access token so it will use it to fetch templates

I am not sure but seems like the encoded base64 presentation of the function config is malformed. can you attach the function configuration file (aka `function.yaml`) you were using to...

Hey @hotlightline , label values adhere to k8s constrains as described [here](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)

Hey @PMazarovich tl;dr - for docker (local) platform - the answer is, it won't expand $(X) variables. That being said, you can use `envsubst` command to generate your `.yaml` and...

Can you elaborate what nuclio version are you using? Indeed looks like a plumbing work is needed, imo just by specifying a secret name on the helm chart and volumize/read...

Looks like these are the needed flags to be plumbed: [--skip-tls-verify](https://github.com/GoogleContainerTools/kaniko#--skip-tls-verify) [--skip-tls-verify-pull](https://github.com/GoogleContainerTools/kaniko#--skip-tls-verify-pull) [--skip-tls-verify-registry](https://github.com/GoogleContainerTools/kaniko#--skip-tls-verify-registry)

You need to set-up docker-registry, so that your function images would be pushed there after build Follow [this](https://github.com/nuclio/nuclio/blob/development/docs/setup/k8s/getting-started-k8s.md) article, to get started with Kubernetes

no, we avoid tls termination to allow better performance. Allowing TLS requires code changes within the HTTP trigger. it is duable but not on our roadmap at the moment.

Hey @ADBurpitt, To tackle CD with nuclio I would highly recommend you to use `github` as function's code entry type and once code is updated, you may export the current...