Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add --helm3 flag to chart app #20

Closed
alexellis opened this issue Feb 26, 2020 · 5 comments
Closed

Add --helm3 flag to chart app #20

alexellis opened this issue Feb 26, 2020 · 5 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed skill/beginner

Comments

@alexellis
Copy link
Owner

Description

Add --helm3 flag to chart app

The arkade install chart command should have helm3 support and use it by default.
@alexellis
Copy link
Owner Author

Derek add label: help wanted, skill/beginner, good first issue

@derek derek bot added good first issue Good for newcomers help wanted Extra attention is needed skill/beginner labels Feb 26, 2020
@kadern0
Copy link
Contributor

kadern0 commented Feb 29, 2020 •
edited

Hi, I've been looking at this one. I have it somehow working, but I get validation errors from helm. Any ideas?

Using kubeconfig: /home/kaderno/.kube/config
Using helm3
Client: x86_64, Linux
2020/02/29 21:15:47 User dir established as: /home/kaderno/.arkade/
"stable" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈ 
VALUES values.yaml
Command: /home/kaderno/.arkade/bin/helm3/helm [upgrade --install nginx-ingress stable/nginx-ingress --namespace default --values /tmp/charts/nginx-ingress/values.yaml --set defaultBackend.enable=false]
Release "nginx-ingress" has been upgraded. Happy Helming!
NAME: nginx-ingress
LAST DEPLOYED: Sat Feb 29 21:16:02 2020
NAMESPACE: default
STATUS: deployed
REVISION: 7
TEST SUITE: None
NOTES:
The nginx-ingress controller has been installed.
It may take a few minutes for the LoadBalancer IP to be available.
You can watch the status by running 'kubectl --namespace default get services -o wide -w nginx-ingress-controller'

An example Ingress that makes use of the controller:

  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      kubernetes.io/ingress.class: nginx
    name: example
    namespace: foo
  spec:
    rules:
      - host: www.example.com
        http:
          paths:
            - backend:
                serviceName: exampleService
                servicePort: 80
              path: /
    # This section is only required if TLS is to be enabled for the Ingress
    tls:
        - hosts:
            - www.example.com
          secretName: example-tls

If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:

  apiVersion: v1
  kind: Secret
  metadata:
    name: example-tls
    namespace: foo
  data:
    tls.crt: <base64 encoded cert>
    tls.key: <base64 encoded key>
  type: kubernetes.io/tls
error validating "/tmp/charts/nginx-ingress/Chart.yaml": error validating data: kind not set; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-customconfig-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-customnodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-headers-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-nodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-tcp-udp-configMapNamespace-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-tcp-udp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-tcp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-default-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-metrics-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-webhook-and-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-webhook-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-autoscaling-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-customconfig-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-customnodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-headers-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-metrics-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-nodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-tcp-udp-configMapNamespace-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-tcp-udp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-tcp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-webhook-and-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-webhook-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error parsing /tmp/charts/nginx-ingress/templates/addheaders-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/clusterrole.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/clusterrolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/job-createSecret.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/job-patchWebhook.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/psp.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/role.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/rolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/serviceaccount.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/validating-webhook.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/clusterrole.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/clusterrolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-daemonset.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-deployment.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-hpa.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-metrics-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-poddisruptionbudget.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-prometheusrules.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-psp.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-role.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-rolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-serviceaccount.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-servicemonitor.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-webhook-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-deployment.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-poddisruptionbudget.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-psp.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-role.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-rolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-serviceaccount.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/proxyheaders-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/tcp-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/udp-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error validating "/tmp/charts/nginx-ingress/values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
Error: kubectl exit code 1, stderr: error validating "/tmp/charts/nginx-ingress/Chart.yaml": error validating data: kind not set; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-customconfig-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-customnodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-headers-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-nodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-tcp-udp-configMapNamespace-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-tcp-udp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/daemonset-tcp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-default-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-metrics-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-webhook-and-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deamonset-webhook-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-autoscaling-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-customconfig-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-customnodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-headers-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-metrics-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-nodeport-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-tcp-udp-configMapNamespace-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-tcp-udp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-tcp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-webhook-and-psp-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error validating "/tmp/charts/nginx-ingress/ci/deployment-webhook-values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
error parsing /tmp/charts/nginx-ingress/templates/addheaders-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/clusterrole.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/clusterrolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/job-createSecret.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/job-patchWebhook.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/psp.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/role.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/rolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/job-patch/serviceaccount.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/admission-webhooks/validating-webhook.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/clusterrole.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/clusterrolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-daemonset.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-deployment.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-hpa.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-metrics-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-poddisruptionbudget.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-prometheusrules.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-psp.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-role.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-rolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-serviceaccount.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-servicemonitor.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/controller-webhook-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-deployment.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-poddisruptionbudget.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-psp.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-role.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-rolebinding.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-service.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/default-backend-serviceaccount.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/proxyheaders-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/tcp-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error parsing /tmp/charts/nginx-ingress/templates/udp-configmap.yaml: json: line 0: invalid character '{' looking for beginning of object key string
error validating "/tmp/charts/nginx-ingress/values.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false

@aidun
Copy link
Contributor

aidun commented Mar 2, 2020

Do you have a PR for this, so we I can watch at your code?

@kadern0 kadern0 mentioned this issue Mar 2, 2020
Closed
@kadern0
Copy link
Contributor

kadern0 commented Mar 2, 2020

Here it is:
#27

@kadern0 kadern0 mentioned this issue Mar 3, 2020
Closed
10 tasks
@alexellis
Copy link
Owner Author

This is no longer required and has been completed

VariableExp0rt pushed a commit to VariableExp0rt/arkade that referenced this issue Jan 4, 2024
# This is a combination of 21 commits.
a34667e 
# This is the 1st commit message:

Update README.md

Signed-off-by: liam.baker <liam.baker@sage.com>

# This is the commit message alexellis#2:

address comments and remove dependency on go-git

Signed-off-by: liam.baker <liam.baker@sage.com>

# This is the commit message alexellis#3:

Fix for regex for downloading Node.js

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#4:

Bump golang.org/x/crypto from 0.14.0 to 0.15.0

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.14.0 to 0.15.0.
- [Commits](golang/crypto@v0.14.0...v0.15.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#5:

Bump golang.org/x/mod from 0.13.0 to 0.14.0

Bumps [golang.org/x/mod](https://github.com/golang/mod) from 0.13.0 to 0.14.0.
- [Commits](golang/mod@v0.13.0...v0.14.0)

---
updated-dependencies:
- dependency-name: golang.org/x/mod
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#6:

Bump github.com/spf13/cobra from 1.7.0 to 1.8.0

Bumps [github.com/spf13/cobra](https://github.com/spf13/cobra) from 1.7.0 to 1.8.0.
- [Release notes](https://github.com/spf13/cobra/releases)
- [Commits](spf13/cobra@v1.7.0...v1.8.0)

---
updated-dependencies:
- dependency-name: github.com/spf13/cobra
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#7:

feat: add kwok to arkade get tools

Signed-off-by: Czékus Máté <mate@picloud.hu>

# This is the commit message alexellis#8:

feat: add kwokctl to arkade get tools

Signed-off-by: Czékus Máté <mate@picloud.hu>

# This is the commit message alexellis#9:

Update system go installation for new format

The endpoint on go.dev now returns additional text after the
version, \ntime.

This change trims off the second half of the output.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#10:

Bump golang.org/x/crypto from 0.15.0 to 0.16.0

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.15.0 to 0.16.0.
- [Commits](golang/crypto@v0.15.0...v0.16.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#11:

Bump github.com/google/go-containerregistry from 0.16.1 to 0.17.0

Bumps [github.com/google/go-containerregistry](https://github.com/google/go-containerregistry) from 0.16.1 to 0.17.0.
- [Release notes](https://github.com/google/go-containerregistry/releases)
- [Changelog](https://github.com/google/go-containerregistry/blob/main/.goreleaser.yml)
- [Commits](google/go-containerregistry@v0.16.1...v0.17.0)

---
updated-dependencies:
- dependency-name: github.com/google/go-containerregistry
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#12:

Add rgee/snowmachine for the festive period

Signed-off-by: Richard Gee <richard@technologee.co.uk>

# This is the commit message alexellis#13:

Bump actions/setup-go from 4 to 5

Bumps [actions/setup-go](https://github.com/actions/setup-go) from 4 to 5.
- [Release notes](https://github.com/actions/setup-go/releases)
- [Commits](actions/setup-go@v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-go
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#14:

Update README.md

Signed-off-by: Alex Ellis <alexellis2@gmail.com>
# This is the commit message alexellis#15:

Export LoadFrom

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#16:

Bump go.mod and vendor

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#17:

Fix issue with version flag for Helm charts

The version was being specified in an invalid way in args
for the helm command via a string with a space. This has been
changed to use a slice.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#18:

Bump golang.org/x/crypto from 0.16.0 to 0.17.0

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.16.0 to 0.17.0.
- [Commits](golang/crypto@v0.16.0...v0.17.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
# This is the commit message alexellis#19:

Move to Go 1.21 for builds and minimum version

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#20:

Limit builds for same SHA

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

# This is the commit message alexellis#21:

Use Go 1.21 for e2e checker

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed skill/beginner
Projects
None yet
Milestone
No milestone
3 participants
@aidun @alexellis @kadern0