feat: add chart scheduling-restart #156

duyet · 2024-03-04T11:37:47Z

No description provided.

…monitoring

duyetbot · 2024-03-04T11:38:59Z

Testing on Kubernetes v1.23.17, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.23.17 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-iekgjgwu21"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-iekgjgwu21
namespace/scheduling-restart-iekgjgwu21 created
>>> helm install scheduling-restart-iekgjgwu21 scheduling-restart --namespace scheduling-restart-iekgjgwu21 --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-iekgjgwu21
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-iekgjgwu21 --sort-by lastTimestamp
No resources found in scheduling-restart-iekgjgwu21 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-iekgjgwu21
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-iekgjgwu21 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-iekgjgwu21"...
>>> helm uninstall scheduling-restart-iekgjgwu21 --namespace scheduling-restart-iekgjgwu21
Error: uninstall: Release not loaded: scheduling-restart-iekgjgwu21: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-iekgjgwu21"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-iekgjgwu21 --timeout 180s
namespace "scheduling-restart-iekgjgwu21" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-iekgjgwu21
Namespace "scheduling-restart-iekgjgwu21" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:39:03Z

Testing on Kubernetes v1.22.5, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.22.5 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-z0wr41k4he"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-z0wr41k4he
namespace/scheduling-restart-z0wr41k4he created
>>> helm install scheduling-restart-z0wr41k4he scheduling-restart --namespace scheduling-restart-z0wr41k4he --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-z0wr41k4he
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-z0wr41k4he --sort-by lastTimestamp
No resources found in scheduling-restart-z0wr41k4he namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-z0wr41k4he
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-z0wr41k4he --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-z0wr41k4he"...
>>> helm uninstall scheduling-restart-z0wr41k4he --namespace scheduling-restart-z0wr41k4he
Error: uninstall: Release not loaded: scheduling-restart-z0wr41k4he: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-z0wr41k4he"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-z0wr41k4he --timeout 180s
namespace "scheduling-restart-z0wr41k4he" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-z0wr41k4he
Namespace "scheduling-restart-z0wr41k4he" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:39:09Z

Testing on Kubernetes v1.24.15, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.24.15 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-2fu8bf826h"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-2fu8bf826h
namespace/scheduling-restart-2fu8bf826h created
>>> helm install scheduling-restart-2fu8bf826h scheduling-restart --namespace scheduling-restart-2fu8bf826h --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-2fu8bf826h
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-2fu8bf826h --sort-by lastTimestamp
No resources found in scheduling-restart-2fu8bf826h namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-2fu8bf826h
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-2fu8bf826h --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-2fu8bf826h"...
>>> helm uninstall scheduling-restart-2fu8bf826h --namespace scheduling-restart-2fu8bf826h
Error: uninstall: Release not loaded: scheduling-restart-2fu8bf826h: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-2fu8bf826h"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-2fu8bf826h --timeout 180s
namespace "scheduling-restart-2fu8bf826h" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-2fu8bf826h
Namespace "scheduling-restart-2fu8bf826h" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:39:10Z

Testing on Kubernetes v1.26.6, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.26.6 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-o7x7a98f93"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-o7x7a98f93
namespace/scheduling-restart-o7x7a98f93 created
>>> helm install scheduling-restart-o7x7a98f93 scheduling-restart --namespace scheduling-restart-o7x7a98f93 --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-o7x7a98f93
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-o7x7a98f93 --sort-by lastTimestamp
No resources found in scheduling-restart-o7x7a98f93 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-o7x7a98f93
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-o7x7a98f93 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-o7x7a98f93"...
>>> helm uninstall scheduling-restart-o7x7a98f93 --namespace scheduling-restart-o7x7a98f93
Error: uninstall: Release not loaded: scheduling-restart-o7x7a98f93: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-o7x7a98f93"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-o7x7a98f93 --timeout 180s
namespace "scheduling-restart-o7x7a98f93" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-o7x7a98f93
Namespace "scheduling-restart-o7x7a98f93" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:39:10Z

Testing on Kubernetes v1.20.15, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.20.15 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-6tzbui77it"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-6tzbui77it
namespace/scheduling-restart-6tzbui77it created
>>> helm install scheduling-restart-6tzbui77it scheduling-restart --namespace scheduling-restart-6tzbui77it --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-6tzbui77it
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-6tzbui77it --sort-by lastTimestamp
No resources found in scheduling-restart-6tzbui77it namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-6tzbui77it
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-6tzbui77it --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-6tzbui77it"...
>>> helm uninstall scheduling-restart-6tzbui77it --namespace scheduling-restart-6tzbui77it
Error: uninstall: Release not loaded: scheduling-restart-6tzbui77it: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-6tzbui77it"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-6tzbui77it --timeout 180s
namespace "scheduling-restart-6tzbui77it" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-6tzbui77it
Namespace "scheduling-restart-6tzbui77it" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:39:28Z

Testing on Kubernetes v1.27.3, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.27.3 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-f00a0h6t18"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-f00a0h6t18
namespace/scheduling-restart-f00a0h6t18 created
>>> helm install scheduling-restart-f00a0h6t18 scheduling-restart --namespace scheduling-restart-f00a0h6t18 --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-f00a0h6t18
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-f00a0h6t18 --sort-by lastTimestamp
No resources found in scheduling-restart-f00a0h6t18 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-f00a0h6t18
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-f00a0h6t18 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-f00a0h6t18"...
>>> helm uninstall scheduling-restart-f00a0h6t18 --namespace scheduling-restart-f00a0h6t18
Error: uninstall: Release not loaded: scheduling-restart-f00a0h6t18: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-f00a0h6t18"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-f00a0h6t18 --timeout 180s
namespace "scheduling-restart-f00a0h6t18" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-f00a0h6t18
Namespace "scheduling-restart-f00a0h6t18" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:39:36Z

Testing on Kubernetes v1.28.0, Helm v3.4.0 ... (Run 8139509686)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.28.0 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only e20f7d5db6de964939e74bc4a172426af4e57c64 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-hhcwqleq0y"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-hhcwqleq0y
namespace/scheduling-restart-hhcwqleq0y created
>>> helm install scheduling-restart-hhcwqleq0y scheduling-restart --namespace scheduling-restart-hhcwqleq0y --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-hhcwqleq0y
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-hhcwqleq0y --sort-by lastTimestamp
........................................................................................................................
<== Events of namespace scheduling-restart-hhcwqleq0y
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-hhcwqleq0y --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-hhcwqleq0y"...
>>> helm uninstall scheduling-restart-hhcwqleq0y --namespace scheduling-restart-hhcwqleq0y
Error: uninstall: Release not loaded: scheduling-restart-hhcwqleq0y: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-hhcwqleq0y"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-hhcwqleq0y --timeout 180s
namespace "scheduling-restart-hhcwqleq0y" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-hhcwqleq0y
Namespace "scheduling-restart-hhcwqleq0y" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:41:01Z

Testing on Kubernetes v1.22.5, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.22.5 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-gl0kysxdk3"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-gl0kysxdk3
namespace/scheduling-restart-gl0kysxdk3 created
>>> helm install scheduling-restart-gl0kysxdk3 scheduling-restart --namespace scheduling-restart-gl0kysxdk3 --wait
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-gl0kysxdk3
........................................................................................................................
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-gl0kysxdk3 --sort-by lastTimestamp
No resources found in scheduling-restart-gl0kysxdk3 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-gl0kysxdk3
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-gl0kysxdk3 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-gl0kysxdk3"...
>>> helm uninstall scheduling-restart-gl0kysxdk3 --namespace scheduling-restart-gl0kysxdk3
Error: uninstall: Release not loaded: scheduling-restart-gl0kysxdk3: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-gl0kysxdk3"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-gl0kysxdk3 --timeout 180s
namespace "scheduling-restart-gl0kysxdk3" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-gl0kysxdk3
Namespace "scheduling-restart-gl0kysxdk3" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:41:08Z

Testing on Kubernetes v1.20.15, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.20.15 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-vy8cm2md90"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-vy8cm2md90
namespace/scheduling-restart-vy8cm2md90 created
>>> helm install scheduling-restart-vy8cm2md90 scheduling-restart --namespace scheduling-restart-vy8cm2md90 --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-vy8cm2md90
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-vy8cm2md90 --sort-by lastTimestamp
No resources found in scheduling-restart-vy8cm2md90 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-vy8cm2md90
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-vy8cm2md90 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-vy8cm2md90"...
>>> helm uninstall scheduling-restart-vy8cm2md90 --namespace scheduling-restart-vy8cm2md90
Error: uninstall: Release not loaded: scheduling-restart-vy8cm2md90: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-vy8cm2md90"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-vy8cm2md90 --timeout 180s
namespace "scheduling-restart-vy8cm2md90" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-vy8cm2md90
Namespace "scheduling-restart-vy8cm2md90" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:41:09Z

Testing on Kubernetes v1.24.15, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.24.15 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-txcxv1y2hx"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-txcxv1y2hx
namespace/scheduling-restart-txcxv1y2hx created
>>> helm install scheduling-restart-txcxv1y2hx scheduling-restart --namespace scheduling-restart-txcxv1y2hx --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-txcxv1y2hx
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-txcxv1y2hx --sort-by lastTimestamp
No resources found in scheduling-restart-txcxv1y2hx namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-txcxv1y2hx
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-txcxv1y2hx --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-txcxv1y2hx"...
>>> helm uninstall scheduling-restart-txcxv1y2hx --namespace scheduling-restart-txcxv1y2hx
Error: uninstall: Release not loaded: scheduling-restart-txcxv1y2hx: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-txcxv1y2hx"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-txcxv1y2hx --timeout 180s
namespace "scheduling-restart-txcxv1y2hx" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-txcxv1y2hx
Namespace "scheduling-restart-txcxv1y2hx" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:41:32Z

Testing on Kubernetes v1.26.6, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.26.6 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-nqir0slev2"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-nqir0slev2
namespace/scheduling-restart-nqir0slev2 created
>>> helm install scheduling-restart-nqir0slev2 scheduling-restart --namespace scheduling-restart-nqir0slev2 --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-nqir0slev2
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-nqir0slev2 --sort-by lastTimestamp
No resources found in scheduling-restart-nqir0slev2 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-nqir0slev2
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-nqir0slev2 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-nqir0slev2"...
>>> helm uninstall scheduling-restart-nqir0slev2 --namespace scheduling-restart-nqir0slev2
Error: uninstall: Release not loaded: scheduling-restart-nqir0slev2: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-nqir0slev2"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-nqir0slev2 --timeout 180s
namespace "scheduling-restart-nqir0slev2" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-nqir0slev2
Namespace "scheduling-restart-nqir0slev2" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:41:36Z

Testing on Kubernetes v1.27.3, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.27.3 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-85m9ryfill"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-85m9ryfill
namespace/scheduling-restart-85m9ryfill created
>>> helm install scheduling-restart-85m9ryfill scheduling-restart --namespace scheduling-restart-85m9ryfill --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-85m9ryfill
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-85m9ryfill --sort-by lastTimestamp
No resources found in scheduling-restart-85m9ryfill namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-85m9ryfill
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-85m9ryfill --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-85m9ryfill"...
>>> helm uninstall scheduling-restart-85m9ryfill --namespace scheduling-restart-85m9ryfill
Error: uninstall: Release not loaded: scheduling-restart-85m9ryfill: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-85m9ryfill"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-85m9ryfill --timeout 180s
namespace "scheduling-restart-85m9ryfill" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-85m9ryfill
Namespace "scheduling-restart-85m9ryfill" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:41:39Z

Testing on Kubernetes v1.23.17, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.23.17 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-qjojter67j"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-qjojter67j
namespace/scheduling-restart-qjojter67j created
>>> helm install scheduling-restart-qjojter67j scheduling-restart --namespace scheduling-restart-qjojter67j --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-qjojter67j
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-qjojter67j --sort-by lastTimestamp
No resources found in scheduling-restart-qjojter67j namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-qjojter67j
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-qjojter67j --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-qjojter67j"...
>>> helm uninstall scheduling-restart-qjojter67j --namespace scheduling-restart-qjojter67j
Error: uninstall: Release not loaded: scheduling-restart-qjojter67j: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-qjojter67j"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-qjojter67j --timeout 180s
namespace "scheduling-restart-qjojter67j" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-qjojter67j
Namespace "scheduling-restart-qjojter67j" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

duyetbot · 2024-03-04T11:42:07Z

Testing on Kubernetes v1.28.0, Helm v3.4.0 ... (Run 8139515541)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.28.0 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 9fe3b7a096797897e2d7169c31de1bb2c0081481 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-5csbdmejxl"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-5csbdmejxl
namespace/scheduling-restart-5csbdmejxl created
>>> helm install scheduling-restart-5csbdmejxl scheduling-restart --namespace scheduling-restart-5csbdmejxl --wait
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(ServiceAccount.metadata): unknown field "automountServiceAccountToken" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-5csbdmejxl
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-5csbdmejxl --sort-by lastTimestamp
No resources found in scheduling-restart-5csbdmejxl namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-5csbdmejxl
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-5csbdmejxl --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-5csbdmejxl"...
>>> helm uninstall scheduling-restart-5csbdmejxl --namespace scheduling-restart-5csbdmejxl
Error: uninstall: Release not loaded: scheduling-restart-5csbdmejxl: release: not found
Error deleting Helm release: failed waiting for process: exit status 1
Deleting namespace "scheduling-restart-5csbdmejxl"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-5csbdmejxl --timeout 180s
namespace "scheduling-restart-5csbdmejxl" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-5csbdmejxl
Namespace "scheduling-restart-5csbdmejxl" terminated.

------------------------------------------------------------------------------------------------------------------------
✖︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart") > failed waiting for process: exit status 1
------------------------------------------------------------------------------------------------------------------------
Error: failed installing charts: failed processing charts
failed installing charts: failed processing charts
failed

…o feat/scheduling-restart

duyetbot · 2024-03-04T12:03:05Z

Testing on Kubernetes v1.20.15, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.20.15 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-8d75rbtk3g"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-8d75rbtk3g
namespace/scheduling-restart-8d75rbtk3g created
>>> helm install scheduling-restart-8d75rbtk3g scheduling-restart --namespace scheduling-restart-8d75rbtk3g --wait
NAME: scheduling-restart-8d75rbtk3g
LAST DEPLOYED: Mon Mar  4 12:04:01 2024
NAMESPACE: scheduling-restart-8d75rbtk3g
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-8d75rbtk3g --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-8d75rbtk3g --namespace scheduling-restart-8d75rbtk3g
NAME: scheduling-restart-8d75rbtk3g
LAST DEPLOYED: Mon Mar  4 12:04:01 2024
NAMESPACE: scheduling-restart-8d75rbtk3g
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-8d75rbtk3g
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-8d75rbtk3g --sort-by lastTimestamp
No resources found in scheduling-restart-8d75rbtk3g namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-8d75rbtk3g
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-8d75rbtk3g --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-8d75rbtk3g"...
>>> helm uninstall scheduling-restart-8d75rbtk3g --namespace scheduling-restart-8d75rbtk3g
release "scheduling-restart-8d75rbtk3g" uninstalled
Deleting namespace "scheduling-restart-8d75rbtk3g"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-8d75rbtk3g --timeout 180s
namespace "scheduling-restart-8d75rbtk3g" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-8d75rbtk3g
Namespace "scheduling-restart-8d75rbtk3g" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2024-03-04T12:03:08Z

Testing on Kubernetes v1.24.15, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.24.15 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-7y522ki30x"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-7y522ki30x
namespace/scheduling-restart-7y522ki30x created
>>> helm install scheduling-restart-7y522ki30x scheduling-restart --namespace scheduling-restart-7y522ki30x --wait
NAME: scheduling-restart-7y522ki30x
LAST DEPLOYED: Mon Mar  4 12:04:05 2024
NAMESPACE: scheduling-restart-7y522ki30x
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-7y522ki30x --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-7y522ki30x --namespace scheduling-restart-7y522ki30x
NAME: scheduling-restart-7y522ki30x
LAST DEPLOYED: Mon Mar  4 12:04:05 2024
NAMESPACE: scheduling-restart-7y522ki30x
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-7y522ki30x
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-7y522ki30x --sort-by lastTimestamp
........................................................................................................................
<== Events of namespace scheduling-restart-7y522ki30x
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-7y522ki30x --selector  --output jsonpath={.items[*].metadata.name}
No resources found in scheduling-restart-7y522ki30x namespace.
========================================================================================================================
Deleting release "scheduling-restart-7y522ki30x"...
>>> helm uninstall scheduling-restart-7y522ki30x --namespace scheduling-restart-7y522ki30x
release "scheduling-restart-7y522ki30x" uninstalled
Deleting namespace "scheduling-restart-7y522ki30x"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-7y522ki30x --timeout 180s
namespace "scheduling-restart-7y522ki30x" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-7y522ki30x
Namespace "scheduling-restart-7y522ki30x" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2024-03-04T12:03:15Z

Testing on Kubernetes v1.26.6, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.26.6 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-4ebr5r2mny"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-4ebr5r2mny
namespace/scheduling-restart-4ebr5r2mny created
>>> helm install scheduling-restart-4ebr5r2mny scheduling-restart --namespace scheduling-restart-4ebr5r2mny --wait
NAME: scheduling-restart-4ebr5r2mny
LAST DEPLOYED: Mon Mar  4 12:04:10 2024
NAMESPACE: scheduling-restart-4ebr5r2mny
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-4ebr5r2mny --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-4ebr5r2mny --namespace scheduling-restart-4ebr5r2mny
NAME: scheduling-restart-4ebr5r2mny
LAST DEPLOYED: Mon Mar  4 12:04:10 2024
NAMESPACE: scheduling-restart-4ebr5r2mny
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-4ebr5r2mny
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-4ebr5r2mny --sort-by lastTimestamp
No resources found in scheduling-restart-4ebr5r2mny namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-4ebr5r2mny
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-4ebr5r2mny --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-4ebr5r2mny"...
>>> helm uninstall scheduling-restart-4ebr5r2mny --namespace scheduling-restart-4ebr5r2mny
release "scheduling-restart-4ebr5r2mny" uninstalled
Deleting namespace "scheduling-restart-4ebr5r2mny"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-4ebr5r2mny --timeout 180s
namespace "scheduling-restart-4ebr5r2mny" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-4ebr5r2mny
Namespace "scheduling-restart-4ebr5r2mny" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2024-03-04T12:03:16Z

Testing on Kubernetes v1.23.17, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.23.17 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-zq3ofgfyil"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-zq3ofgfyil
namespace/scheduling-restart-zq3ofgfyil created
>>> helm install scheduling-restart-zq3ofgfyil scheduling-restart --namespace scheduling-restart-zq3ofgfyil --wait
NAME: scheduling-restart-zq3ofgfyil
LAST DEPLOYED: Mon Mar  4 12:04:13 2024
NAMESPACE: scheduling-restart-zq3ofgfyil
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-zq3ofgfyil --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-zq3ofgfyil --namespace scheduling-restart-zq3ofgfyil
NAME: scheduling-restart-zq3ofgfyil
LAST DEPLOYED: Mon Mar  4 12:04:13 2024
NAMESPACE: scheduling-restart-zq3ofgfyil
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-zq3ofgfyil
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-zq3ofgfyil --sort-by lastTimestamp
No resources found in scheduling-restart-zq3ofgfyil namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-zq3ofgfyil
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-zq3ofgfyil --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-zq3ofgfyil"...
>>> helm uninstall scheduling-restart-zq3ofgfyil --namespace scheduling-restart-zq3ofgfyil
release "scheduling-restart-zq3ofgfyil" uninstalled
Deleting namespace "scheduling-restart-zq3ofgfyil"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-zq3ofgfyil --timeout 180s
namespace "scheduling-restart-zq3ofgfyil" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-zq3ofgfyil
Namespace "scheduling-restart-zq3ofgfyil" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2024-03-04T12:03:21Z

Testing on Kubernetes v1.22.5, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.22.5 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-1wa0cz7mgy"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-1wa0cz7mgy
namespace/scheduling-restart-1wa0cz7mgy created
>>> helm install scheduling-restart-1wa0cz7mgy scheduling-restart --namespace scheduling-restart-1wa0cz7mgy --wait
NAME: scheduling-restart-1wa0cz7mgy
LAST DEPLOYED: Mon Mar  4 12:04:34 2024
NAMESPACE: scheduling-restart-1wa0cz7mgy
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-1wa0cz7mgy --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-1wa0cz7mgy --namespace scheduling-restart-1wa0cz7mgy
NAME: scheduling-restart-1wa0cz7mgy
LAST DEPLOYED: Mon Mar  4 12:04:34 2024
NAMESPACE: scheduling-restart-1wa0cz7mgy
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-1wa0cz7mgy
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-1wa0cz7mgy --sort-by lastTimestamp
No resources found in scheduling-restart-1wa0cz7mgy namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-1wa0cz7mgy
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-1wa0cz7mgy --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-1wa0cz7mgy"...
>>> helm uninstall scheduling-restart-1wa0cz7mgy --namespace scheduling-restart-1wa0cz7mgy
release "scheduling-restart-1wa0cz7mgy" uninstalled
Deleting namespace "scheduling-restart-1wa0cz7mgy"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-1wa0cz7mgy --timeout 180s
namespace "scheduling-restart-1wa0cz7mgy" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-1wa0cz7mgy
Namespace "scheduling-restart-1wa0cz7mgy" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2024-03-04T12:03:47Z

Testing on Kubernetes v1.27.3, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.27.3 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-ipo6urzye4"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-ipo6urzye4
namespace/scheduling-restart-ipo6urzye4 created
>>> helm install scheduling-restart-ipo6urzye4 scheduling-restart --namespace scheduling-restart-ipo6urzye4 --wait
NAME: scheduling-restart-ipo6urzye4
LAST DEPLOYED: Mon Mar  4 12:04:37 2024
NAMESPACE: scheduling-restart-ipo6urzye4
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-ipo6urzye4 --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-ipo6urzye4 --namespace scheduling-restart-ipo6urzye4
NAME: scheduling-restart-ipo6urzye4
LAST DEPLOYED: Mon Mar  4 12:04:37 2024
NAMESPACE: scheduling-restart-ipo6urzye4
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-ipo6urzye4
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-ipo6urzye4 --sort-by lastTimestamp
No resources found in scheduling-restart-ipo6urzye4 namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-ipo6urzye4
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-ipo6urzye4 --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-ipo6urzye4"...
>>> helm uninstall scheduling-restart-ipo6urzye4 --namespace scheduling-restart-ipo6urzye4
release "scheduling-restart-ipo6urzye4" uninstalled
Deleting namespace "scheduling-restart-ipo6urzye4"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-ipo6urzye4 --timeout 180s
namespace "scheduling-restart-ipo6urzye4" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-ipo6urzye4
Namespace "scheduling-restart-ipo6urzye4" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2024-03-04T12:04:21Z

Testing on Kubernetes v1.28.0, Helm v3.4.0 ... (Run 8139800196)

Linting chart successfully 🚀.

Creating KinD cluster ...
Created KinD cluster v1.28.0 successfully.
Installing charts and validating ...

Testing chart successfully. :hooray:

Installing charts...
>>> helm version --template {{ .Version }}
>>> git rev-parse --is-inside-work-tree
>>> git rev-parse --verify origin/master
>>> git merge-base origin/master HEAD
>>> git diff --find-renames --name-only 8e29707dfb93175fc15b8e0d764210298720362e -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------

>>> helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" already exists with the same configuration, skipping
>>> helm repo add stable https://charts.helm.sh/stable --force-update
"stable" has been added to your repositories
>>> helm dependency build scheduling-restart
Installing chart "scheduling-restart => (version: \"0.1.0\", path: \"scheduling-restart\")"...
Creating namespace "scheduling-restart-7v3ch8ectn"...
>>> kubectl --request-timeout=30s create namespace scheduling-restart-7v3ch8ectn
namespace/scheduling-restart-7v3ch8ectn created
>>> helm install scheduling-restart-7v3ch8ectn scheduling-restart --namespace scheduling-restart-7v3ch8ectn --wait
NAME: scheduling-restart-7v3ch8ectn
LAST DEPLOYED: Mon Mar  4 12:05:22 2024
NAMESPACE: scheduling-restart-7v3ch8ectn
STATUS: deployed
REVISION: 1
TEST SUITE: None
>>> kubectl --request-timeout=30s get deployments --namespace scheduling-restart-7v3ch8ectn --selector  --output jsonpath={.items[*].metadata.name}
>>> helm test scheduling-restart-7v3ch8ectn --namespace scheduling-restart-7v3ch8ectn
NAME: scheduling-restart-7v3ch8ectn
LAST DEPLOYED: Mon Mar  4 12:05:22 2024
NAMESPACE: scheduling-restart-7v3ch8ectn
STATUS: deployed
REVISION: 1
TEST SUITE: None
========================================================================================================================
........................................................................................................................
==> Events of namespace scheduling-restart-7v3ch8ectn
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace scheduling-restart-7v3ch8ectn --sort-by lastTimestamp
No resources found in scheduling-restart-7v3ch8ectn namespace.
........................................................................................................................
<== Events of namespace scheduling-restart-7v3ch8ectn
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace scheduling-restart-7v3ch8ectn --selector  --output jsonpath={.items[*].metadata.name}
========================================================================================================================
Deleting release "scheduling-restart-7v3ch8ectn"...
>>> helm uninstall scheduling-restart-7v3ch8ectn --namespace scheduling-restart-7v3ch8ectn
release "scheduling-restart-7v3ch8ectn" uninstalled
Deleting namespace "scheduling-restart-7v3ch8ectn"...
>>> kubectl --request-timeout=30s delete namespace scheduling-restart-7v3ch8ectn --timeout 180s
namespace "scheduling-restart-7v3ch8ectn" deleted
>>> kubectl --request-timeout=30s get namespace scheduling-restart-7v3ch8ectn
Namespace "scheduling-restart-7v3ch8ectn" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ scheduling-restart => (version: "0.1.0", path: "scheduling-restart")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyet and others added 4 commits February 28, 2024 22:00

feat(clickhouse-monitoring): can customize service port and portName

6682410

Merge branch 'master' of github.com:duyet/charts into fix/clickhouse-…

5131102

…monitoring

feat: add chart scheduling-restart

e0f9c71

Merge branch 'master' into feat/scheduling-restart

e5dcd28

duyet added 2 commits March 4, 2024 19:02

fix: remove automountServiceAccountToken

b7bafd7

Merge branch 'feat/scheduling-restart' of github.com:duyet/charts int…

8bd61cd

…o feat/scheduling-restart

duyet merged commit 15f28d0 into master Mar 4, 2024
15 checks passed

duyet deleted the feat/scheduling-restart branch March 4, 2024 12:06

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add chart scheduling-restart #156

feat: add chart scheduling-restart #156

duyet commented Mar 4, 2024

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

feat: add chart scheduling-restart #156

feat: add chart scheduling-restart #156

Conversation

duyet commented Mar 4, 2024

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 • edited Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading

duyetbot commented Mar 4, 2024 •

edited

Loading