Update alpine/curl Docker tag to v8.23.0 by renovate[bot] · Pull Request #240 · duyet/charts

renovate · 2026-09-05T04:23:22Z

This PR contains the following updates:

Package	Update	Change
alpine/curl	minor	`8.21.0` → `8.23.0`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

duyetbot · 2026-09-05T04:24:06Z

Testing on Kubernetes v1.29.10, Helm v3.14.0 ... (Run 33944418186)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Installing chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"...
Creating namespace "clickhouse-monitoring-e5ymnnbrix"...
>>> kubectl --request-timeout=30s create namespace clickhouse-monitoring-e5ymnnbrix
namespace/clickhouse-monitoring-e5ymnnbrix created
>>> helm install clickhouse-monitoring-e5ymnnbrix clickhouse-monitoring --namespace clickhouse-monitoring-e5ymnnbrix --wait
NAME: clickhouse-monitoring-e5ymnnbrix
LAST DEPLOYED: Sat Sep  5 04:25:04 2026
NAMESPACE: clickhouse-monitoring-e5ymnnbrix
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-e5ymnnbrix -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-e5ymnnbrix" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-e5ymnnbrix $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-e5ymnnbrix port-forward $POD_NAME 8080:$CONTAINER_PORT
>>> kubectl --request-timeout=30s get deployments --namespace clickhouse-monitoring-e5ymnnbrix --selector  --output jsonpath={.items[*].metadata.name}
>>> kubectl --request-timeout=30s rollout status deployment clickhouse-monitoring-e5ymnnbrix --namespace clickhouse-monitoring-e5ymnnbrix
deployment "clickhouse-monitoring-e5ymnnbrix" successfully rolled out
>>> kubectl --request-timeout=30s get deployment clickhouse-monitoring-e5ymnnbrix --namespace clickhouse-monitoring-e5ymnnbrix --output jsonpath={.status.unavailableReplicas}
>>> helm test clickhouse-monitoring-e5ymnnbrix --namespace clickhouse-monitoring-e5ymnnbrix
NAME: clickhouse-monitoring-e5ymnnbrix
LAST DEPLOYED: Sat Sep  5 04:25:04 2026
NAMESPACE: clickhouse-monitoring-e5ymnnbrix
STATUS: deployed
REVISION: 1
TEST SUITE:     clickhouse-monitoring-e5ymnnbrix-test-connection
Last Started:   Sat Sep  5 04:25:10 2026
Last Completed: Sat Sep  5 04:25:14 2026
Phase:          Succeeded
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-e5ymnnbrix -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-e5ymnnbrix" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-e5ymnnbrix $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-e5ymnnbrix port-forward $POD_NAME 8080:$CONTAINER_PORT
========================================================================================================================
........................................................................................................................
==> Events of namespace clickhouse-monitoring-e5ymnnbrix
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace clickhouse-monitoring-e5ymnnbrix --sort-by lastTimestamp
LAST SEEN   TYPE     REASON              OBJECT                                                  SUBOBJECT                                SOURCE                                 MESSAGE                                                                                                                                  FIRST SEEN   COUNT   NAME
10s         Normal   Scheduled           pod/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd                                             default-scheduler                      Successfully assigned clickhouse-monitoring-e5ymnnbrix/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd to chart-testing-control-plane   10s          1       clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd.18d2522120f0590c
10s         Normal   Pulling             pod/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"                                                                               10s          1       clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd.18d2522138bbd2f8
10s         Normal   SuccessfulCreate    replicaset/clickhouse-monitoring-e5ymnnbrix-549d7fbd5                                            replicaset-controller                  Created pod: clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd                                                                            10s          1       clickhouse-monitoring-e5ymnnbrix-549d7fbd5.18d2522120c9ccae
10s         Normal   ScalingReplicaSet   deployment/clickhouse-monitoring-e5ymnnbrix                                                      deployment-controller                  Scaled up replica set clickhouse-monitoring-e5ymnnbrix-549d7fbd5 to 1                                                                    10s          1       clickhouse-monitoring-e5ymnnbrix.18d252212067c589
7s          Normal   Pulled              pod/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.805s (2.805s including waiting)                              7s           1       clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd.18d25221dff20c08
7s          Normal   Created             pod/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Created container clickhouse-monitoring                                                                                                  7s           1       clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd.18d25221e05e9cf4
7s          Normal   Started             pod/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Started container clickhouse-monitoring                                                                                                  7s           1       clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd.18d25221e4efd854
4s          Normal   Scheduled           pod/clickhouse-monitoring-e5ymnnbrix-test-connection                                             default-scheduler                      Successfully assigned clickhouse-monitoring-e5ymnnbrix/clickhouse-monitoring-e5ymnnbrix-test-connection to chart-testing-control-plane   4s           1       clickhouse-monitoring-e5ymnnbrix-test-connection.18d25222965e9567
4s          Normal   Pulling             pod/clickhouse-monitoring-e5ymnnbrix-test-connection    spec.containers{wget}                    kubelet, chart-testing-control-plane   Pulling image "busybox"                                                                                                                  4s           1       clickhouse-monitoring-e5ymnnbrix-test-connection.18d25222ae1543bf
3s          Normal   Pulled              pod/clickhouse-monitoring-e5ymnnbrix-test-connection    spec.containers{wget}                    kubelet, chart-testing-control-plane   Successfully pulled image "busybox" in 711ms (711ms including waiting)                                                                   3s           1       clickhouse-monitoring-e5ymnnbrix-test-connection.18d25222d88467cf
3s          Normal   Created             pod/clickhouse-monitoring-e5ymnnbrix-test-connection    spec.containers{wget}                    kubelet, chart-testing-control-plane   Created container wget                                                                                                                   3s           1       clickhouse-monitoring-e5ymnnbrix-test-connection.18d25222d90be552
3s          Normal   Started             pod/clickhouse-monitoring-e5ymnnbrix-test-connection    spec.containers{wget}                    kubelet, chart-testing-control-plane   Started container wget                                                                                                                   3s           1       clickhouse-monitoring-e5ymnnbrix-test-connection.18d25222ddc93108
........................................................................................................................
<== Events of namespace clickhouse-monitoring-e5ymnnbrix
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace clickhouse-monitoring-e5ymnnbrix --selector  --output jsonpath={.items[*].metadata.name}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd --namespace clickhouse-monitoring-e5ymnnbrix
Name:             clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd
Namespace:        clickhouse-monitoring-e5ymnnbrix
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:04 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-e5ymnnbrix
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
                pod-template-hash=549d7fbd5
Annotations:      <none>
Status:           Running
IP:               10.244.0.5
IPs:
IP:           10.244.0.5
Controlled By:  ReplicaSet/clickhouse-monitoring-e5ymnnbrix-549d7fbd5
Containers:
clickhouse-monitoring:
  Container ID:   containerd://90e0c27951ed785ba0f3af2eb9b0c296cff76313b426a6ba44cbe42160231e64
  Image:          ghcr.io/duyet/clickhouse-monitoring:latest
  Image ID:       ghcr.io/duyet/clickhouse-monitoring@sha256:84edfe8a67a8271ff17dba9107e6e7e55229e9a094dcaea9494ee9f587295dc4
  Port:           3000/TCP
  Host Port:      0/TCP
  State:          Running
    Started:      Sat, 05 Sep 2026 04:25:07 +0000
  Ready:          True
  Restart Count:  0
  Liveness:       http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Readiness:      http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Environment:
    CLICKHOUSE_HOST:      http://localhost:8123
    CLICKHOUSE_USER:      default
    CLICKHOUSE_PASSWORD:  
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hjwdd (ro)
Conditions:
Type                        Status
PodReadyToStartContainers   True 
Initialized                 True 
Ready                       True 
ContainersReady             True 
PodScheduled                True 
Volumes:
kube-api-access-hjwdd:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  10s   default-scheduler  Successfully assigned clickhouse-monitoring-e5ymnnbrix/clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd to chart-testing-control-plane
Normal  Pulling    10s   kubelet            Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"
Normal  Pulled     7s    kubelet            Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.805s (2.805s including waiting)
Normal  Created    7s    kubelet            Created container clickhouse-monitoring
Normal  Started    7s    kubelet            Started container clickhouse-monitoring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd --no-headers --namespace clickhouse-monitoring-e5ymnnbrix --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd --no-headers --namespace clickhouse-monitoring-e5ymnnbrix --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd --namespace clickhouse-monitoring-e5ymnnbrix --container clickhouse-monitoring
➜ Listening on: http://localhost:3000/ (all interfaces)
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-e5ymnnbrix-549d7fbd5-4xmkd
------------------------------------------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-e5ymnnbrix-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-e5ymnnbrix-test-connection --namespace clickhouse-monitoring-e5ymnnbrix
Name:             clickhouse-monitoring-e5ymnnbrix-test-connection
Namespace:        clickhouse-monitoring-e5ymnnbrix
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:10 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-e5ymnnbrix
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
Annotations:      helm.sh/hook: test
Status:           Succeeded
IP:               10.244.0.6
IPs:
IP:  10.244.0.6
Containers:
wget:
  Container ID:  containerd://ad2662da6ac6c21ec2c505193ad57be478cb96aac830465e7841d8848ca4fb19
  Image:         busybox
  Image ID:      docker.io/library/busybox@sha256:dc2d74b28e4cf8984fa52af1f39bc7c3d9c73760b41a74d629f5d11b1ab28616
  Port:          <none>
  Host Port:     <none>
  Command:
    wget
  Args:
    clickhouse-monitoring-e5ymnnbrix:3000
  State:          Terminated
    Reason:       Completed
    Exit Code:    0
    Started:      Sat, 05 Sep 2026 04:25:11 +0000
    Finished:     Sat, 05 Sep 2026 04:25:12 +0000
  Ready:          False
  Restart Count:  0
  Environment:    <none>
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zglh9 (ro)
Conditions:
Type                        Status
PodReadyToStartContainers   False 
Initialized                 True 
Ready                       False 
ContainersReady             False 
PodScheduled                True 
Volumes:
kube-api-access-zglh9:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  4s    default-scheduler  Successfully assigned clickhouse-monitoring-e5ymnnbrix/clickhouse-monitoring-e5ymnnbrix-test-connection to chart-testing-control-plane
Normal  Pulling    4s    kubelet            Pulling image "busybox"
Normal  Pulled     3s    kubelet            Successfully pulled image "busybox" in 711ms (711ms including waiting)
Normal  Created    3s    kubelet            Created container wget
Normal  Started    3s    kubelet            Started container wget
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-e5ymnnbrix-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-e5ymnnbrix-test-connection --no-headers --namespace clickhouse-monitoring-e5ymnnbrix --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-e5ymnnbrix-test-connection --no-headers --namespace clickhouse-monitoring-e5ymnnbrix --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-e5ymnnbrix-test-connection
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-e5ymnnbrix-test-connection --namespace clickhouse-monitoring-e5ymnnbrix --container wget
Connecting to clickhouse-monitoring-e5ymnnbrix:3000 (10.96.114.216:3000)
saving to 'index.html'
index.html           100% |********************************| 71589  0:00:00 ETA
'index.html' saved
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-e5ymnnbrix-test-connection
------------------------------------------------------------------------------------------------------------------------
========================================================================================================================
Deleting release "clickhouse-monitoring-e5ymnnbrix"...
>>> helm uninstall clickhouse-monitoring-e5ymnnbrix --namespace clickhouse-monitoring-e5ymnnbrix --wait
release "clickhouse-monitoring-e5ymnnbrix" uninstalled
Deleting namespace "clickhouse-monitoring-e5ymnnbrix"...
>>> kubectl --request-timeout=30s delete namespace clickhouse-monitoring-e5ymnnbrix --timeout 180s
namespace "clickhouse-monitoring-e5ymnnbrix" deleted
>>> kubectl --request-timeout=30s get namespace clickhouse-monitoring-e5ymnnbrix
Namespace "clickhouse-monitoring-e5ymnnbrix" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-05T04:24:10Z

Testing on Kubernetes v1.27.16, Helm v3.14.0 ... (Run 33944418186)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Installing chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"...
Creating namespace "clickhouse-monitoring-d5pc1gysim"...
>>> kubectl --request-timeout=30s create namespace clickhouse-monitoring-d5pc1gysim
namespace/clickhouse-monitoring-d5pc1gysim created
>>> helm install clickhouse-monitoring-d5pc1gysim clickhouse-monitoring --namespace clickhouse-monitoring-d5pc1gysim --wait
NAME: clickhouse-monitoring-d5pc1gysim
LAST DEPLOYED: Sat Sep  5 04:25:08 2026
NAMESPACE: clickhouse-monitoring-d5pc1gysim
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-d5pc1gysim -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-d5pc1gysim" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-d5pc1gysim $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-d5pc1gysim port-forward $POD_NAME 8080:$CONTAINER_PORT
>>> kubectl --request-timeout=30s get deployments --namespace clickhouse-monitoring-d5pc1gysim --selector  --output jsonpath={.items[*].metadata.name}
>>> kubectl --request-timeout=30s rollout status deployment clickhouse-monitoring-d5pc1gysim --namespace clickhouse-monitoring-d5pc1gysim
deployment "clickhouse-monitoring-d5pc1gysim" successfully rolled out
>>> kubectl --request-timeout=30s get deployment clickhouse-monitoring-d5pc1gysim --namespace clickhouse-monitoring-d5pc1gysim --output jsonpath={.status.unavailableReplicas}
>>> helm test clickhouse-monitoring-d5pc1gysim --namespace clickhouse-monitoring-d5pc1gysim
NAME: clickhouse-monitoring-d5pc1gysim
LAST DEPLOYED: Sat Sep  5 04:25:08 2026
NAMESPACE: clickhouse-monitoring-d5pc1gysim
STATUS: deployed
REVISION: 1
TEST SUITE:     clickhouse-monitoring-d5pc1gysim-test-connection
Last Started:   Sat Sep  5 04:25:12 2026
Last Completed: Sat Sep  5 04:25:16 2026
Phase:          Succeeded
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-d5pc1gysim -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-d5pc1gysim" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-d5pc1gysim $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-d5pc1gysim port-forward $POD_NAME 8080:$CONTAINER_PORT
========================================================================================================================
........................................................................................................................
==> Events of namespace clickhouse-monitoring-d5pc1gysim
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace clickhouse-monitoring-d5pc1gysim --sort-by lastTimestamp
LAST SEEN   TYPE     REASON              OBJECT                                                   SUBOBJECT                                SOURCE                                 MESSAGE                                                                                                                                   FIRST SEEN   COUNT   NAME
8s          Normal   Scheduled           pod/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs                                             default-scheduler                      Successfully assigned clickhouse-monitoring-d5pc1gysim/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs to chart-testing-control-plane   8s           1       clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs.18d252222a1d6a5c
8s          Normal   SuccessfulCreate    replicaset/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8                                            replicaset-controller                  Created pod: clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs                                                                            8s           1       clickhouse-monitoring-d5pc1gysim-5c6bbc7db8.18d25222299dc3b8
8s          Normal   ScalingReplicaSet   deployment/clickhouse-monitoring-d5pc1gysim                                                       deployment-controller                  Scaled up replica set clickhouse-monitoring-d5pc1gysim-5c6bbc7db8 to 1                                                                    8s           1       clickhouse-monitoring-d5pc1gysim.18d2522229252407
7s          Normal   Pulling             pod/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"                                                                                7s           1       clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs.18d2522242533b85
5s          Normal   Pulled              pod/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.037355048s (2.037372271s including waiting)                   5s           1       clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs.18d25222bbc345bf
5s          Normal   Created             pod/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Created container clickhouse-monitoring                                                                                                   5s           1       clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs.18d25222bc32b3c4
5s          Normal   Started             pod/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Started container clickhouse-monitoring                                                                                                   5s           1       clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs.18d25222c158def7
4s          Normal   Scheduled           pod/clickhouse-monitoring-d5pc1gysim-test-connection                                              default-scheduler                      Successfully assigned clickhouse-monitoring-d5pc1gysim/clickhouse-monitoring-d5pc1gysim-test-connection to chart-testing-control-plane    4s           1       clickhouse-monitoring-d5pc1gysim-test-connection.18d2522327b0a4ed
3s          Normal   Pulling             pod/clickhouse-monitoring-d5pc1gysim-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Pulling image "busybox"                                                                                                                   3s           1       clickhouse-monitoring-d5pc1gysim-test-connection.18d252233fab9c16
2s          Normal   Pulled              pod/clickhouse-monitoring-d5pc1gysim-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Successfully pulled image "busybox" in 696.561616ms (696.597431ms including waiting)                                                      2s           1       clickhouse-monitoring-d5pc1gysim-test-connection.18d2522369313525
2s          Normal   Created             pod/clickhouse-monitoring-d5pc1gysim-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Created container wget                                                                                                                    2s           1       clickhouse-monitoring-d5pc1gysim-test-connection.18d2522369aabc17
2s          Normal   Started             pod/clickhouse-monitoring-d5pc1gysim-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Started container wget                                                                                                                    2s           1       clickhouse-monitoring-d5pc1gysim-test-connection.18d252236e5e3491
........................................................................................................................
<== Events of namespace clickhouse-monitoring-d5pc1gysim
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace clickhouse-monitoring-d5pc1gysim --selector  --output jsonpath={.items[*].metadata.name}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs --namespace clickhouse-monitoring-d5pc1gysim
Name:             clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs
Namespace:        clickhouse-monitoring-d5pc1gysim
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:08 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-d5pc1gysim
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
                pod-template-hash=5c6bbc7db8
Annotations:      <none>
Status:           Running
IP:               10.244.0.5
IPs:
IP:           10.244.0.5
Controlled By:  ReplicaSet/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8
Containers:
clickhouse-monitoring:
  Container ID:   containerd://5e4d2e0ec4bf36730aa94a40995808410d50f45bc8cbcd18f66f2b4f8e3264d7
  Image:          ghcr.io/duyet/clickhouse-monitoring:latest
  Image ID:       ghcr.io/duyet/clickhouse-monitoring@sha256:84edfe8a67a8271ff17dba9107e6e7e55229e9a094dcaea9494ee9f587295dc4
  Port:           3000/TCP
  Host Port:      0/TCP
  State:          Running
    Started:      Sat, 05 Sep 2026 04:25:11 +0000
  Ready:          True
  Restart Count:  0
  Liveness:       http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Readiness:      http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Environment:
    CLICKHOUSE_HOST:      http://localhost:8123
    CLICKHOUSE_USER:      default
    CLICKHOUSE_PASSWORD:  
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-2tck5 (ro)
Conditions:
Type              Status
Initialized       True 
Ready             True 
ContainersReady   True 
PodScheduled      True 
Volumes:
kube-api-access-2tck5:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  8s    default-scheduler  Successfully assigned clickhouse-monitoring-d5pc1gysim/clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs to chart-testing-control-plane
Normal  Pulling    7s    kubelet            Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"
Normal  Pulled     5s    kubelet            Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.037355048s (2.037372271s including waiting)
Normal  Created    5s    kubelet            Created container clickhouse-monitoring
Normal  Started    5s    kubelet            Started container clickhouse-monitoring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs --no-headers --namespace clickhouse-monitoring-d5pc1gysim --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs --no-headers --namespace clickhouse-monitoring-d5pc1gysim --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs --namespace clickhouse-monitoring-d5pc1gysim --container clickhouse-monitoring
➜ Listening on: http://localhost:3000/ (all interfaces)
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-d5pc1gysim-5c6bbc7db8-kstgs
------------------------------------------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-d5pc1gysim-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-d5pc1gysim-test-connection --namespace clickhouse-monitoring-d5pc1gysim
Name:             clickhouse-monitoring-d5pc1gysim-test-connection
Namespace:        clickhouse-monitoring-d5pc1gysim
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:12 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-d5pc1gysim
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
Annotations:      helm.sh/hook: test
Status:           Succeeded
IP:               
IPs:              <none>
Containers:
wget:
  Container ID:  containerd://f95828fc072a9010a6791763a0dca1f266c192b36ab26744f54e9d6263582ad4
  Image:         busybox
  Image ID:      docker.io/library/busybox@sha256:dc2d74b28e4cf8984fa52af1f39bc7c3d9c73760b41a74d629f5d11b1ab28616
  Port:          <none>
  Host Port:     <none>
  Command:
    wget
  Args:
    clickhouse-monitoring-d5pc1gysim:3000
  State:          Terminated
    Reason:       Completed
    Exit Code:    0
    Started:      Sat, 05 Sep 2026 04:25:14 +0000
    Finished:     Sat, 05 Sep 2026 04:25:14 +0000
  Ready:          False
  Restart Count:  0
  Environment:    <none>
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lg2d7 (ro)
Conditions:
Type              Status
Initialized       True 
Ready             False 
ContainersReady   False 
PodScheduled      True 
Volumes:
kube-api-access-lg2d7:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  4s    default-scheduler  Successfully assigned clickhouse-monitoring-d5pc1gysim/clickhouse-monitoring-d5pc1gysim-test-connection to chart-testing-control-plane
Normal  Pulling    3s    kubelet            Pulling image "busybox"
Normal  Pulled     2s    kubelet            Successfully pulled image "busybox" in 696.561616ms (696.597431ms including waiting)
Normal  Created    2s    kubelet            Created container wget
Normal  Started    2s    kubelet            Started container wget
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-d5pc1gysim-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-d5pc1gysim-test-connection --no-headers --namespace clickhouse-monitoring-d5pc1gysim --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-d5pc1gysim-test-connection --no-headers --namespace clickhouse-monitoring-d5pc1gysim --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-d5pc1gysim-test-connection
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-d5pc1gysim-test-connection --namespace clickhouse-monitoring-d5pc1gysim --container wget
Connecting to clickhouse-monitoring-d5pc1gysim:3000 (10.96.227.70:3000)
saving to 'index.html'
index.html           100% |********************************| 71589  0:00:00 ETA
'index.html' saved
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-d5pc1gysim-test-connection
------------------------------------------------------------------------------------------------------------------------
========================================================================================================================
Deleting release "clickhouse-monitoring-d5pc1gysim"...
>>> helm uninstall clickhouse-monitoring-d5pc1gysim --namespace clickhouse-monitoring-d5pc1gysim --wait
release "clickhouse-monitoring-d5pc1gysim" uninstalled
Deleting namespace "clickhouse-monitoring-d5pc1gysim"...
>>> kubectl --request-timeout=30s delete namespace clickhouse-monitoring-d5pc1gysim --timeout 180s
namespace "clickhouse-monitoring-d5pc1gysim" deleted
>>> kubectl --request-timeout=30s get namespace clickhouse-monitoring-d5pc1gysim
Namespace "clickhouse-monitoring-d5pc1gysim" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-05T04:24:11Z

Testing on Kubernetes v1.30.6, Helm v3.14.0 ... (Run 33944418186)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Installing chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"...
Creating namespace "clickhouse-monitoring-luxt42qgu5"...
>>> kubectl --request-timeout=30s create namespace clickhouse-monitoring-luxt42qgu5
namespace/clickhouse-monitoring-luxt42qgu5 created
>>> helm install clickhouse-monitoring-luxt42qgu5 clickhouse-monitoring --namespace clickhouse-monitoring-luxt42qgu5 --wait
NAME: clickhouse-monitoring-luxt42qgu5
LAST DEPLOYED: Sat Sep  5 04:25:10 2026
NAMESPACE: clickhouse-monitoring-luxt42qgu5
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-luxt42qgu5 -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-luxt42qgu5" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-luxt42qgu5 $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-luxt42qgu5 port-forward $POD_NAME 8080:$CONTAINER_PORT
>>> kubectl --request-timeout=30s get deployments --namespace clickhouse-monitoring-luxt42qgu5 --selector  --output jsonpath={.items[*].metadata.name}
>>> kubectl --request-timeout=30s rollout status deployment clickhouse-monitoring-luxt42qgu5 --namespace clickhouse-monitoring-luxt42qgu5
deployment "clickhouse-monitoring-luxt42qgu5" successfully rolled out
>>> kubectl --request-timeout=30s get deployment clickhouse-monitoring-luxt42qgu5 --namespace clickhouse-monitoring-luxt42qgu5 --output jsonpath={.status.unavailableReplicas}
>>> helm test clickhouse-monitoring-luxt42qgu5 --namespace clickhouse-monitoring-luxt42qgu5
NAME: clickhouse-monitoring-luxt42qgu5
LAST DEPLOYED: Sat Sep  5 04:25:10 2026
NAMESPACE: clickhouse-monitoring-luxt42qgu5
STATUS: deployed
REVISION: 1
TEST SUITE:     clickhouse-monitoring-luxt42qgu5-test-connection
Last Started:   Sat Sep  5 04:25:16 2026
Last Completed: Sat Sep  5 04:25:21 2026
Phase:          Succeeded
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-luxt42qgu5 -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-luxt42qgu5" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-luxt42qgu5 $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-luxt42qgu5 port-forward $POD_NAME 8080:$CONTAINER_PORT
========================================================================================================================
........................................................................................................................
==> Events of namespace clickhouse-monitoring-luxt42qgu5
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace clickhouse-monitoring-luxt42qgu5 --sort-by lastTimestamp
LAST SEEN   TYPE     REASON              OBJECT                                                 SUBOBJECT                                SOURCE                                 MESSAGE                                                                                                                                  FIRST SEEN   COUNT   NAME
11s         Normal   Scheduled           pod/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8                                             default-scheduler                      Successfully assigned clickhouse-monitoring-luxt42qgu5/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8 to chart-testing-control-plane    11s          1       clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8.18d25222a1033c7a
11s         Normal   SuccessfulCreate    replicaset/clickhouse-monitoring-luxt42qgu5-96b9bf67                                            replicaset-controller                  Created pod: clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8                                                                             11s          1       clickhouse-monitoring-luxt42qgu5-96b9bf67.18d25222a08d7a55
11s         Normal   ScalingReplicaSet   deployment/clickhouse-monitoring-luxt42qgu5                                                     deployment-controller                  Scaled up replica set clickhouse-monitoring-luxt42qgu5-96b9bf67 to 1                                                                     11s          1       clickhouse-monitoring-luxt42qgu5.18d25222a031943f
10s         Normal   Pulling             pod/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"                                                                               10s          1       clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8.18d25222b9a84403
7s          Normal   Pulled              pod/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 3.61s (3.61s including waiting). Image size: 68646506 bytes.   7s           1       clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8.18d2522390dbfb54
7s          Normal   Created             pod/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Created container clickhouse-monitoring                                                                                                  7s           1       clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8.18d252239153309f
7s          Normal   Started             pod/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Started container clickhouse-monitoring                                                                                                  7s           1       clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8.18d25223969a200b
5s          Normal   Scheduled           pod/clickhouse-monitoring-luxt42qgu5-test-connection                                            default-scheduler                      Successfully assigned clickhouse-monitoring-luxt42qgu5/clickhouse-monitoring-luxt42qgu5-test-connection to chart-testing-control-plane   5s           1       clickhouse-monitoring-luxt42qgu5-test-connection.18d252241727cf0e
4s          Normal   Pulling             pod/clickhouse-monitoring-luxt42qgu5-test-connection   spec.containers{wget}                    kubelet, chart-testing-control-plane   Pulling image "busybox"                                                                                                                  4s           1       clickhouse-monitoring-luxt42qgu5-test-connection.18d252242f2b7f07
3s          Normal   Pulled              pod/clickhouse-monitoring-luxt42qgu5-test-connection   spec.containers{wget}                    kubelet, chart-testing-control-plane   Successfully pulled image "busybox" in 1.439s (1.439s including waiting). Image size: 2236931 bytes.                                     3s           1       clickhouse-monitoring-luxt42qgu5-test-connection.18d2522484f5c1b7
3s          Normal   Created             pod/clickhouse-monitoring-luxt42qgu5-test-connection   spec.containers{wget}                    kubelet, chart-testing-control-plane   Created container wget                                                                                                                   3s           1       clickhouse-monitoring-luxt42qgu5-test-connection.18d25224856835dc
3s          Normal   Started             pod/clickhouse-monitoring-luxt42qgu5-test-connection   spec.containers{wget}                    kubelet, chart-testing-control-plane   Started container wget                                                                                                                   3s           1       clickhouse-monitoring-luxt42qgu5-test-connection.18d252248a5867da
........................................................................................................................
<== Events of namespace clickhouse-monitoring-luxt42qgu5
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace clickhouse-monitoring-luxt42qgu5 --selector  --output jsonpath={.items[*].metadata.name}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8 --namespace clickhouse-monitoring-luxt42qgu5
Name:             clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8
Namespace:        clickhouse-monitoring-luxt42qgu5
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:10 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-luxt42qgu5
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
                pod-template-hash=96b9bf67
Annotations:      <none>
Status:           Running
IP:               10.244.0.5
IPs:
IP:           10.244.0.5
Controlled By:  ReplicaSet/clickhouse-monitoring-luxt42qgu5-96b9bf67
Containers:
clickhouse-monitoring:
  Container ID:   containerd://49f81a6c67c0ad1d0eef96013cd2ff438359c2c17b54a1863bac988230b11f0d
  Image:          ghcr.io/duyet/clickhouse-monitoring:latest
  Image ID:       ghcr.io/duyet/clickhouse-monitoring@sha256:84edfe8a67a8271ff17dba9107e6e7e55229e9a094dcaea9494ee9f587295dc4
  Port:           3000/TCP
  Host Port:      0/TCP
  State:          Running
    Started:      Sat, 05 Sep 2026 04:25:14 +0000
  Ready:          True
  Restart Count:  0
  Liveness:       http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Readiness:      http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Environment:
    CLICKHOUSE_HOST:      http://localhost:8123
    CLICKHOUSE_USER:      default
    CLICKHOUSE_PASSWORD:  
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9vh4d (ro)
Conditions:
Type                        Status
PodReadyToStartContainers   True 
Initialized                 True 
Ready                       True 
ContainersReady             True 
PodScheduled                True 
Volumes:
kube-api-access-9vh4d:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  11s   default-scheduler  Successfully assigned clickhouse-monitoring-luxt42qgu5/clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8 to chart-testing-control-plane
Normal  Pulling    10s   kubelet            Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"
Normal  Pulled     7s    kubelet            Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 3.61s (3.61s including waiting). Image size: 68646506 bytes.
Normal  Created    7s    kubelet            Created container clickhouse-monitoring
Normal  Started    7s    kubelet            Started container clickhouse-monitoring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8 --no-headers --namespace clickhouse-monitoring-luxt42qgu5 --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8 --no-headers --namespace clickhouse-monitoring-luxt42qgu5 --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8 --namespace clickhouse-monitoring-luxt42qgu5 --container clickhouse-monitoring
➜ Listening on: http://localhost:3000/ (all interfaces)
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-luxt42qgu5-96b9bf67-m76w8
------------------------------------------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-luxt42qgu5-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-luxt42qgu5-test-connection --namespace clickhouse-monitoring-luxt42qgu5
Name:             clickhouse-monitoring-luxt42qgu5-test-connection
Namespace:        clickhouse-monitoring-luxt42qgu5
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:16 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-luxt42qgu5
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
Annotations:      helm.sh/hook: test
Status:           Succeeded
IP:               10.244.0.6
IPs:
IP:  10.244.0.6
Containers:
wget:
  Container ID:  containerd://8577fa785b44dc54339cb430f0d3ae1646be16e67748233be0f63175eab2cf42
  Image:         busybox
  Image ID:      docker.io/library/busybox@sha256:dc2d74b28e4cf8984fa52af1f39bc7c3d9c73760b41a74d629f5d11b1ab28616
  Port:          <none>
  Host Port:     <none>
  Command:
    wget
  Args:
    clickhouse-monitoring-luxt42qgu5:3000
  State:          Terminated
    Reason:       Completed
    Exit Code:    0
    Started:      Sat, 05 Sep 2026 04:25:18 +0000
    Finished:     Sat, 05 Sep 2026 04:25:19 +0000
  Ready:          False
  Restart Count:  0
  Environment:    <none>
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hl97s (ro)
Conditions:
Type                        Status
PodReadyToStartContainers   False 
Initialized                 True 
Ready                       False 
ContainersReady             False 
PodScheduled                True 
Volumes:
kube-api-access-hl97s:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  5s    default-scheduler  Successfully assigned clickhouse-monitoring-luxt42qgu5/clickhouse-monitoring-luxt42qgu5-test-connection to chart-testing-control-plane
Normal  Pulling    4s    kubelet            Pulling image "busybox"
Normal  Pulled     3s    kubelet            Successfully pulled image "busybox" in 1.439s (1.439s including waiting). Image size: 2236931 bytes.
Normal  Created    3s    kubelet            Created container wget
Normal  Started    3s    kubelet            Started container wget
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-luxt42qgu5-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-luxt42qgu5-test-connection --no-headers --namespace clickhouse-monitoring-luxt42qgu5 --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-luxt42qgu5-test-connection --no-headers --namespace clickhouse-monitoring-luxt42qgu5 --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-luxt42qgu5-test-connection
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-luxt42qgu5-test-connection --namespace clickhouse-monitoring-luxt42qgu5 --container wget
Connecting to clickhouse-monitoring-luxt42qgu5:3000 (10.96.32.127:3000)
saving to 'index.html'
index.html           100% |********************************| 71589  0:00:00 ETA
'index.html' saved
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-luxt42qgu5-test-connection
------------------------------------------------------------------------------------------------------------------------
========================================================================================================================
Deleting release "clickhouse-monitoring-luxt42qgu5"...
>>> helm uninstall clickhouse-monitoring-luxt42qgu5 --namespace clickhouse-monitoring-luxt42qgu5 --wait
release "clickhouse-monitoring-luxt42qgu5" uninstalled
Deleting namespace "clickhouse-monitoring-luxt42qgu5"...
>>> kubectl --request-timeout=30s delete namespace clickhouse-monitoring-luxt42qgu5 --timeout 180s
namespace "clickhouse-monitoring-luxt42qgu5" deleted
>>> kubectl --request-timeout=30s get namespace clickhouse-monitoring-luxt42qgu5
Namespace "clickhouse-monitoring-luxt42qgu5" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-05T04:24:13Z

Testing on Kubernetes v1.28.13, Helm v3.14.0 ... (Run 33944418186)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Installing chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"...
Creating namespace "clickhouse-monitoring-0zhqtzd1zt"...
>>> kubectl --request-timeout=30s create namespace clickhouse-monitoring-0zhqtzd1zt
namespace/clickhouse-monitoring-0zhqtzd1zt created
>>> helm install clickhouse-monitoring-0zhqtzd1zt clickhouse-monitoring --namespace clickhouse-monitoring-0zhqtzd1zt --wait
NAME: clickhouse-monitoring-0zhqtzd1zt
LAST DEPLOYED: Sat Sep  5 04:25:11 2026
NAMESPACE: clickhouse-monitoring-0zhqtzd1zt
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-0zhqtzd1zt -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-0zhqtzd1zt" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-0zhqtzd1zt $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-0zhqtzd1zt port-forward $POD_NAME 8080:$CONTAINER_PORT
>>> kubectl --request-timeout=30s get deployments --namespace clickhouse-monitoring-0zhqtzd1zt --selector  --output jsonpath={.items[*].metadata.name}
>>> kubectl --request-timeout=30s rollout status deployment clickhouse-monitoring-0zhqtzd1zt --namespace clickhouse-monitoring-0zhqtzd1zt
deployment "clickhouse-monitoring-0zhqtzd1zt" successfully rolled out
>>> kubectl --request-timeout=30s get deployment clickhouse-monitoring-0zhqtzd1zt --namespace clickhouse-monitoring-0zhqtzd1zt --output jsonpath={.status.unavailableReplicas}
>>> helm test clickhouse-monitoring-0zhqtzd1zt --namespace clickhouse-monitoring-0zhqtzd1zt
NAME: clickhouse-monitoring-0zhqtzd1zt
LAST DEPLOYED: Sat Sep  5 04:25:11 2026
NAMESPACE: clickhouse-monitoring-0zhqtzd1zt
STATUS: deployed
REVISION: 1
TEST SUITE:     clickhouse-monitoring-0zhqtzd1zt-test-connection
Last Started:   Sat Sep  5 04:25:17 2026
Last Completed: Sat Sep  5 04:25:22 2026
Phase:          Succeeded
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-0zhqtzd1zt -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-0zhqtzd1zt" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-0zhqtzd1zt $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-0zhqtzd1zt port-forward $POD_NAME 8080:$CONTAINER_PORT
========================================================================================================================
........................................................................................................................
==> Events of namespace clickhouse-monitoring-0zhqtzd1zt
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace clickhouse-monitoring-0zhqtzd1zt --sort-by lastTimestamp
LAST SEEN   TYPE     REASON              OBJECT                                                   SUBOBJECT                                SOURCE                                 MESSAGE                                                                                                                                   FIRST SEEN   COUNT   NAME
11s         Normal   Scheduled           pod/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw                                             default-scheduler                      Successfully assigned clickhouse-monitoring-0zhqtzd1zt/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw to chart-testing-control-plane   11s          1       clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw.18d25222d4195cdf
11s         Normal   Pulling             pod/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"                                                                                11s          1       clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw.18d25222eb9addf7
11s         Normal   SuccessfulCreate    replicaset/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56                                            replicaset-controller                  Created pod: clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw                                                                            11s          1       clickhouse-monitoring-0zhqtzd1zt-5f4db48b56.18d25222d3aae09c
11s         Normal   ScalingReplicaSet   deployment/clickhouse-monitoring-0zhqtzd1zt                                                       deployment-controller                  Scaled up replica set clickhouse-monitoring-0zhqtzd1zt-5f4db48b56 to 1                                                                    11s          1       clickhouse-monitoring-0zhqtzd1zt.18d25222d3347473
8s          Normal   Pulled              pod/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.485s (2.485s including waiting)                               8s           1       clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw.18d252237fbe6fed
8s          Normal   Created             pod/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Created container clickhouse-monitoring                                                                                                   8s           1       clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw.18d252238026c08e
8s          Normal   Started             pod/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Started container clickhouse-monitoring                                                                                                   8s           1       clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw.18d2522384f3d084
5s          Normal   Scheduled           pod/clickhouse-monitoring-0zhqtzd1zt-test-connection                                              default-scheduler                      Successfully assigned clickhouse-monitoring-0zhqtzd1zt/clickhouse-monitoring-0zhqtzd1zt-test-connection to chart-testing-control-plane    5s           1       clickhouse-monitoring-0zhqtzd1zt-test-connection.18d2522449836128
4s          Normal   Pulling             pod/clickhouse-monitoring-0zhqtzd1zt-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Pulling image "busybox"                                                                                                                   4s           1       clickhouse-monitoring-0zhqtzd1zt-test-connection.18d25224619ca95e
3s          Normal   Pulled              pod/clickhouse-monitoring-0zhqtzd1zt-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Successfully pulled image "busybox" in 1.116s (1.116s including waiting)                                                                  3s           1       clickhouse-monitoring-0zhqtzd1zt-test-connection.18d25224a4297ae3
3s          Normal   Created             pod/clickhouse-monitoring-0zhqtzd1zt-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Created container wget                                                                                                                    3s           1       clickhouse-monitoring-0zhqtzd1zt-test-connection.18d25224a4977046
3s          Normal   Started             pod/clickhouse-monitoring-0zhqtzd1zt-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Started container wget                                                                                                                    3s           1       clickhouse-monitoring-0zhqtzd1zt-test-connection.18d25224a8f7369c
........................................................................................................................
<== Events of namespace clickhouse-monitoring-0zhqtzd1zt
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace clickhouse-monitoring-0zhqtzd1zt --selector  --output jsonpath={.items[*].metadata.name}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw --namespace clickhouse-monitoring-0zhqtzd1zt
Name:             clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw
Namespace:        clickhouse-monitoring-0zhqtzd1zt
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:11 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-0zhqtzd1zt
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
                pod-template-hash=5f4db48b56
Annotations:      <none>
Status:           Running
IP:               10.244.0.5
IPs:
IP:           10.244.0.5
Controlled By:  ReplicaSet/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56
Containers:
clickhouse-monitoring:
  Container ID:   containerd://488461e03439543f860bb3848c47905a64e2f097515ff6f7b30b41c50defd5c1
  Image:          ghcr.io/duyet/clickhouse-monitoring:latest
  Image ID:       ghcr.io/duyet/clickhouse-monitoring@sha256:84edfe8a67a8271ff17dba9107e6e7e55229e9a094dcaea9494ee9f587295dc4
  Port:           3000/TCP
  Host Port:      0/TCP
  State:          Running
    Started:      Sat, 05 Sep 2026 04:25:14 +0000
  Ready:          True
  Restart Count:  0
  Liveness:       http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Readiness:      http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Environment:
    CLICKHOUSE_HOST:      http://localhost:8123
    CLICKHOUSE_USER:      default
    CLICKHOUSE_PASSWORD:  
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-8kdb2 (ro)
Conditions:
Type              Status
Initialized       True 
Ready             True 
ContainersReady   True 
PodScheduled      True 
Volumes:
kube-api-access-8kdb2:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  11s   default-scheduler  Successfully assigned clickhouse-monitoring-0zhqtzd1zt/clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw to chart-testing-control-plane
Normal  Pulling    11s   kubelet            Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"
Normal  Pulled     8s    kubelet            Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.485s (2.485s including waiting)
Normal  Created    8s    kubelet            Created container clickhouse-monitoring
Normal  Started    8s    kubelet            Started container clickhouse-monitoring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw --no-headers --namespace clickhouse-monitoring-0zhqtzd1zt --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw --no-headers --namespace clickhouse-monitoring-0zhqtzd1zt --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw --namespace clickhouse-monitoring-0zhqtzd1zt --container clickhouse-monitoring
➜ Listening on: http://localhost:3000/ (all interfaces)
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-0zhqtzd1zt-5f4db48b56-wqgnw
------------------------------------------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-0zhqtzd1zt-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-0zhqtzd1zt-test-connection --namespace clickhouse-monitoring-0zhqtzd1zt
Name:             clickhouse-monitoring-0zhqtzd1zt-test-connection
Namespace:        clickhouse-monitoring-0zhqtzd1zt
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:17 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-0zhqtzd1zt
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
Annotations:      helm.sh/hook: test
Status:           Succeeded
IP:               10.244.0.6
IPs:
IP:  10.244.0.6
Containers:
wget:
  Container ID:  containerd://664e7baa9de1f03a2553dd75e6b7d45251341f6de1a34f7fc7e33c51a989f13d
  Image:         busybox
  Image ID:      docker.io/library/busybox@sha256:dc2d74b28e4cf8984fa52af1f39bc7c3d9c73760b41a74d629f5d11b1ab28616
  Port:          <none>
  Host Port:     <none>
  Command:
    wget
  Args:
    clickhouse-monitoring-0zhqtzd1zt:3000
  State:          Terminated
    Reason:       Completed
    Exit Code:    0
    Started:      Sat, 05 Sep 2026 04:25:19 +0000
    Finished:     Sat, 05 Sep 2026 04:25:19 +0000
  Ready:          False
  Restart Count:  0
  Environment:    <none>
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-n88lh (ro)
Conditions:
Type              Status
Initialized       True 
Ready             False 
ContainersReady   False 
PodScheduled      True 
Volumes:
kube-api-access-n88lh:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  5s    default-scheduler  Successfully assigned clickhouse-monitoring-0zhqtzd1zt/clickhouse-monitoring-0zhqtzd1zt-test-connection to chart-testing-control-plane
Normal  Pulling    4s    kubelet            Pulling image "busybox"
Normal  Pulled     3s    kubelet            Successfully pulled image "busybox" in 1.116s (1.116s including waiting)
Normal  Created    3s    kubelet            Created container wget
Normal  Started    3s    kubelet            Started container wget
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-0zhqtzd1zt-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-0zhqtzd1zt-test-connection --no-headers --namespace clickhouse-monitoring-0zhqtzd1zt --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-0zhqtzd1zt-test-connection --no-headers --namespace clickhouse-monitoring-0zhqtzd1zt --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-0zhqtzd1zt-test-connection
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-0zhqtzd1zt-test-connection --namespace clickhouse-monitoring-0zhqtzd1zt --container wget
Connecting to clickhouse-monitoring-0zhqtzd1zt:3000 (10.96.157.100:3000)
saving to 'index.html'
index.html           100% |********************************| 71589  0:00:00 ETA
'index.html' saved
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-0zhqtzd1zt-test-connection
------------------------------------------------------------------------------------------------------------------------
========================================================================================================================
Deleting release "clickhouse-monitoring-0zhqtzd1zt"...
>>> helm uninstall clickhouse-monitoring-0zhqtzd1zt --namespace clickhouse-monitoring-0zhqtzd1zt --wait
release "clickhouse-monitoring-0zhqtzd1zt" uninstalled
Deleting namespace "clickhouse-monitoring-0zhqtzd1zt"...
>>> kubectl --request-timeout=30s delete namespace clickhouse-monitoring-0zhqtzd1zt --timeout 180s
namespace "clickhouse-monitoring-0zhqtzd1zt" deleted
>>> kubectl --request-timeout=30s get namespace clickhouse-monitoring-0zhqtzd1zt
Namespace "clickhouse-monitoring-0zhqtzd1zt" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-05T04:24:17Z

Testing on Kubernetes v1.31.2, Helm v3.14.0 ... (Run 33944418186)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 22470ebe3134206679b40c35319266d49c2763d5 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Installing chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"...
Creating namespace "clickhouse-monitoring-sssn3ymztz"...
>>> kubectl --request-timeout=30s create namespace clickhouse-monitoring-sssn3ymztz
namespace/clickhouse-monitoring-sssn3ymztz created
>>> helm install clickhouse-monitoring-sssn3ymztz clickhouse-monitoring --namespace clickhouse-monitoring-sssn3ymztz --wait
NAME: clickhouse-monitoring-sssn3ymztz
LAST DEPLOYED: Sat Sep  5 04:25:11 2026
NAMESPACE: clickhouse-monitoring-sssn3ymztz
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-sssn3ymztz -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-sssn3ymztz" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-sssn3ymztz $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-sssn3ymztz port-forward $POD_NAME 8080:$CONTAINER_PORT
>>> kubectl --request-timeout=30s get deployments --namespace clickhouse-monitoring-sssn3ymztz --selector  --output jsonpath={.items[*].metadata.name}
>>> kubectl --request-timeout=30s rollout status deployment clickhouse-monitoring-sssn3ymztz --namespace clickhouse-monitoring-sssn3ymztz
deployment "clickhouse-monitoring-sssn3ymztz" successfully rolled out
>>> kubectl --request-timeout=30s get deployment clickhouse-monitoring-sssn3ymztz --namespace clickhouse-monitoring-sssn3ymztz --output jsonpath={.status.unavailableReplicas}
>>> helm test clickhouse-monitoring-sssn3ymztz --namespace clickhouse-monitoring-sssn3ymztz
NAME: clickhouse-monitoring-sssn3ymztz
LAST DEPLOYED: Sat Sep  5 04:25:11 2026
NAMESPACE: clickhouse-monitoring-sssn3ymztz
STATUS: deployed
REVISION: 1
TEST SUITE:     clickhouse-monitoring-sssn3ymztz-test-connection
Last Started:   Sat Sep  5 04:25:18 2026
Last Completed: Sat Sep  5 04:25:23 2026
Phase:          Succeeded
NOTES:
1. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace clickhouse-monitoring-sssn3ymztz -l "app.kubernetes.io/name=clickhouse-monitoring,app.kubernetes.io/instance=clickhouse-monitoring-sssn3ymztz" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace clickhouse-monitoring-sssn3ymztz $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace clickhouse-monitoring-sssn3ymztz port-forward $POD_NAME 8080:$CONTAINER_PORT
========================================================================================================================
........................................................................................................................
==> Events of namespace clickhouse-monitoring-sssn3ymztz
........................................................................................................................
>>> kubectl --request-timeout=30s get events --output wide --namespace clickhouse-monitoring-sssn3ymztz --sort-by lastTimestamp
LAST SEEN   TYPE     REASON              OBJECT                                                   SUBOBJECT                                SOURCE                                 MESSAGE                                                                                                                                   FIRST SEEN   COUNT   NAME
12s         Normal   Scheduled           pod/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p                                             default-scheduler                      Successfully assigned clickhouse-monitoring-sssn3ymztz/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p to chart-testing-control-plane   12s          1       clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p.18d25222e42813a9
12s         Normal   SuccessfulCreate    replicaset/clickhouse-monitoring-sssn3ymztz-75b7cc9949                                            replicaset-controller                  Created pod: clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p                                                                            12s          1       clickhouse-monitoring-sssn3ymztz-75b7cc9949.18d25222e3d95533
12s         Normal   ScalingReplicaSet   deployment/clickhouse-monitoring-sssn3ymztz                                                       deployment-controller                  Scaled up replica set clickhouse-monitoring-sssn3ymztz-75b7cc9949 to 1                                                                    12s          1       clickhouse-monitoring-sssn3ymztz.18d25222e37efbd0
11s         Normal   Pulling             pod/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"                                                                                11s          1       clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p.18d25222fbd750fb
9s          Normal   Pulled              pod/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.76s (2.76s including waiting). Image size: 68646506 bytes.    9s           1       clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p.18d25223a05d560a
9s          Normal   Created             pod/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Created container clickhouse-monitoring                                                                                                   9s           1       clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p.18d25223a0ca2f92
8s          Normal   Started             pod/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p    spec.containers{clickhouse-monitoring}   kubelet, chart-testing-control-plane   Started container clickhouse-monitoring                                                                                                   8s           1       clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p.18d25223a55bf979
5s          Normal   Scheduled           pod/clickhouse-monitoring-sssn3ymztz-test-connection                                              default-scheduler                      Successfully assigned clickhouse-monitoring-sssn3ymztz/clickhouse-monitoring-sssn3ymztz-test-connection to chart-testing-control-plane    5s           1       clickhouse-monitoring-sssn3ymztz-test-connection.18d25224727ca387
5s          Normal   Pulling             pod/clickhouse-monitoring-sssn3ymztz-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Pulling image "busybox"                                                                                                                   5s           1       clickhouse-monitoring-sssn3ymztz-test-connection.18d252248a39304d
4s          Normal   Pulled              pod/clickhouse-monitoring-sssn3ymztz-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Successfully pulled image "busybox" in 644ms (644ms including waiting). Image size: 2236931 bytes.                                        4s           1       clickhouse-monitoring-sssn3ymztz-test-connection.18d25224b0a76bee
4s          Normal   Created             pod/clickhouse-monitoring-sssn3ymztz-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Created container wget                                                                                                                    4s           1       clickhouse-monitoring-sssn3ymztz-test-connection.18d25224b1292b90
4s          Normal   Started             pod/clickhouse-monitoring-sssn3ymztz-test-connection     spec.containers{wget}                    kubelet, chart-testing-control-plane   Started container wget                                                                                                                    4s           1       clickhouse-monitoring-sssn3ymztz-test-connection.18d25224b80d194b
........................................................................................................................
<== Events of namespace clickhouse-monitoring-sssn3ymztz
........................................................................................................................
>>> kubectl --request-timeout=30s get pods --no-headers --namespace clickhouse-monitoring-sssn3ymztz --selector  --output jsonpath={.items[*].metadata.name}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p --namespace clickhouse-monitoring-sssn3ymztz
Name:             clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p
Namespace:        clickhouse-monitoring-sssn3ymztz
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:11 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-sssn3ymztz
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
                pod-template-hash=75b7cc9949
Annotations:      <none>
Status:           Running
IP:               10.244.0.5
IPs:
IP:           10.244.0.5
Controlled By:  ReplicaSet/clickhouse-monitoring-sssn3ymztz-75b7cc9949
Containers:
clickhouse-monitoring:
  Container ID:   containerd://ec19087d8bc72ea447a4caa38b81d8ab67e8f015d3d51669212aa1dab3de134c
  Image:          ghcr.io/duyet/clickhouse-monitoring:latest
  Image ID:       ghcr.io/duyet/clickhouse-monitoring@sha256:84edfe8a67a8271ff17dba9107e6e7e55229e9a094dcaea9494ee9f587295dc4
  Port:           3000/TCP
  Host Port:      0/TCP
  State:          Running
    Started:      Sat, 05 Sep 2026 04:25:15 +0000
  Ready:          True
  Restart Count:  0
  Liveness:       http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Readiness:      http-get http://:http/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
  Environment:
    CLICKHOUSE_HOST:      http://localhost:8123
    CLICKHOUSE_USER:      default
    CLICKHOUSE_PASSWORD:  
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-56dgv (ro)
Conditions:
Type                        Status
PodReadyToStartContainers   True 
Initialized                 True 
Ready                       True 
ContainersReady             True 
PodScheduled                True 
Volumes:
kube-api-access-56dgv:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  12s   default-scheduler  Successfully assigned clickhouse-monitoring-sssn3ymztz/clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p to chart-testing-control-plane
Normal  Pulling    11s   kubelet            Pulling image "ghcr.io/duyet/clickhouse-monitoring:latest"
Normal  Pulled     9s    kubelet            Successfully pulled image "ghcr.io/duyet/clickhouse-monitoring:latest" in 2.76s (2.76s including waiting). Image size: 68646506 bytes.
Normal  Created    9s    kubelet            Created container clickhouse-monitoring
Normal  Started    8s    kubelet            Started container clickhouse-monitoring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p --no-headers --namespace clickhouse-monitoring-sssn3ymztz --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p --no-headers --namespace clickhouse-monitoring-sssn3ymztz --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p --namespace clickhouse-monitoring-sssn3ymztz --container clickhouse-monitoring
➜ Listening on: http://localhost:3000/ (all interfaces)
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-sssn3ymztz-75b7cc9949-9vq2p
------------------------------------------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> Description of pod clickhouse-monitoring-sssn3ymztz-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s describe pod clickhouse-monitoring-sssn3ymztz-test-connection --namespace clickhouse-monitoring-sssn3ymztz
Name:             clickhouse-monitoring-sssn3ymztz-test-connection
Namespace:        clickhouse-monitoring-sssn3ymztz
Priority:         0
Service Account:  default
Node:             chart-testing-control-plane/172.18.0.2
Start Time:       Sat, 05 Sep 2026 04:25:18 +0000
Labels:           app.kubernetes.io/instance=clickhouse-monitoring-sssn3ymztz
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=clickhouse-monitoring
                app.kubernetes.io/version=1.16.0
                helm.sh/chart=clickhouse-monitoring-0.1.2
Annotations:      helm.sh/hook: test
Status:           Succeeded
IP:               10.244.0.6
IPs:
IP:  10.244.0.6
Containers:
wget:
  Container ID:  containerd://893c7534d767810364fd3eaa37cd9b777c117a12e5ec0a04d5268f19b00698ef
  Image:         busybox
  Image ID:      docker.io/library/busybox@sha256:dc2d74b28e4cf8984fa52af1f39bc7c3d9c73760b41a74d629f5d11b1ab28616
  Port:          <none>
  Host Port:     <none>
  Command:
    wget
  Args:
    clickhouse-monitoring-sssn3ymztz:3000
  State:          Terminated
    Reason:       Completed
    Exit Code:    0
    Started:      Sat, 05 Sep 2026 04:25:19 +0000
    Finished:     Sat, 05 Sep 2026 04:25:20 +0000
  Ready:          False
  Restart Count:  0
  Environment:    <none>
  Mounts:
    /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-bs86j (ro)
Conditions:
Type                        Status
PodReadyToStartContainers   False 
Initialized                 True 
Ready                       False 
ContainersReady             False 
PodScheduled                True 
Volumes:
kube-api-access-bs86j:
  Type:                    Projected (a volume that contains injected data from multiple sources)
  TokenExpirationSeconds:  3607
  ConfigMapName:           kube-root-ca.crt
  ConfigMapOptional:       <nil>
  DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                           node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type    Reason     Age   From               Message
----    ------     ----  ----               -------
Normal  Scheduled  5s    default-scheduler  Successfully assigned clickhouse-monitoring-sssn3ymztz/clickhouse-monitoring-sssn3ymztz-test-connection to chart-testing-control-plane
Normal  Pulling    5s    kubelet            Pulling image "busybox"
Normal  Pulled     4s    kubelet            Successfully pulled image "busybox" in 644ms (644ms including waiting). Image size: 2236931 bytes.
Normal  Created    4s    kubelet            Created container wget
Normal  Started    4s    kubelet            Started container wget
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<== Description of pod clickhouse-monitoring-sssn3ymztz-test-connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-sssn3ymztz-test-connection --no-headers --namespace clickhouse-monitoring-sssn3ymztz --output jsonpath={.spec.initContainers[*].name}
>>> kubectl --request-timeout=30s get pods clickhouse-monitoring-sssn3ymztz-test-connection --no-headers --namespace clickhouse-monitoring-sssn3ymztz --output jsonpath={.spec.containers[*].name}
------------------------------------------------------------------------------------------------------------------------
==> Logs of container clickhouse-monitoring-sssn3ymztz-test-connection
------------------------------------------------------------------------------------------------------------------------
>>> kubectl --request-timeout=30s logs clickhouse-monitoring-sssn3ymztz-test-connection --namespace clickhouse-monitoring-sssn3ymztz --container wget
Connecting to clickhouse-monitoring-sssn3ymztz:3000 (10.96.137.55:3000)
saving to 'index.html'
index.html           100% |********************************| 71589  0:00:00 ETA
'index.html' saved
------------------------------------------------------------------------------------------------------------------------
<== Logs of container clickhouse-monitoring-sssn3ymztz-test-connection
------------------------------------------------------------------------------------------------------------------------
========================================================================================================================
Deleting release "clickhouse-monitoring-sssn3ymztz"...
>>> helm uninstall clickhouse-monitoring-sssn3ymztz --namespace clickhouse-monitoring-sssn3ymztz --wait
release "clickhouse-monitoring-sssn3ymztz" uninstalled
Deleting namespace "clickhouse-monitoring-sssn3ymztz"...
>>> kubectl --request-timeout=30s delete namespace clickhouse-monitoring-sssn3ymztz --timeout 180s
namespace "clickhouse-monitoring-sssn3ymztz" deleted
>>> kubectl --request-timeout=30s get namespace clickhouse-monitoring-sssn3ymztz
Namespace "clickhouse-monitoring-sssn3ymztz" terminated.

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

coderabbitai · 2026-09-18T16:12:42Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: bcb40a2a-9827-408c-b24f-1f55273ef4f6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

Trigger review

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

duyetbot · 2026-09-18T16:13:23Z

Testing on Kubernetes v1.31.2, Helm v3.14.0 ... (Run 35367100698)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 150b80967c55fe97da69ebb61ba899eba35dd444 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 150b80967c55fe97da69ebb61ba899eba35dd444 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-18T16:13:24Z

Testing on Kubernetes v1.30.6, Helm v3.14.0 ... (Run 35367100698)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 150b80967c55fe97da69ebb61ba899eba35dd444 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 150b80967c55fe97da69ebb61ba899eba35dd444 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-18T16:13:28Z

Testing on Kubernetes v1.29.10, Helm v3.14.0 ... (Run 35367100698)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 150b80967c55fe97da69ebb61ba899eba35dd444 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 150b80967c55fe97da69ebb61ba899eba35dd444 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-18T16:13:33Z

Testing on Kubernetes v1.27.16, Helm v3.14.0 ... (Run 35367100698)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 150b80967c55fe97da69ebb61ba899eba35dd444 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 150b80967c55fe97da69ebb61ba899eba35dd444 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-18T16:13:44Z

Testing on Kubernetes v1.28.13, Helm v3.14.0 ... (Run 35367100698)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 150b80967c55fe97da69ebb61ba899eba35dd444 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.2\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.2", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 150b80967c55fe97da69ebb61ba899eba35dd444 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-25T00:55:51Z

Testing on Kubernetes v1.30.6, Helm v3.14.0 ... (Run 36079529815)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-25T00:57:50Z

Testing on Kubernetes v1.31.2, Helm v3.14.0 ... (Run 36079529815)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-25T00:57:57Z

Testing on Kubernetes v1.28.13, Helm v3.14.0 ... (Run 36079529815)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-25T00:57:59Z

Testing on Kubernetes v1.27.16, Helm v3.14.0 ... (Run 36079529815)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-09-25T00:58:01Z

Testing on Kubernetes v1.29.10, Helm v3.14.0 ... (Run 36079529815)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-10-31T04:29:32Z

Testing on Kubernetes v1.27.16, Helm v3.14.0 ... (Run 41168719072)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-10-31T04:29:33Z

Testing on Kubernetes v1.30.6, Helm v3.14.0 ... (Run 41168719072)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-10-31T04:29:33Z

Testing on Kubernetes v1.31.2, Helm v3.14.0 ... (Run 41168719072)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-10-31T04:29:36Z

Testing on Kubernetes v1.28.13, Helm v3.14.0 ... (Run 41168719072)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

duyetbot · 2026-10-31T04:29:51Z

Testing on Kubernetes v1.29.10, Helm v3.14.0 ... (Run 41168719072)
clickhouse-monitoring

Linting chart successfully 🚀.

Linting 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 cc941978cae3b374acfffb16289baa675e62d692 -- .

------------------------------------------------------------------------------------------------------------------------
Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------

>>> 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 clickhouse-monitoring
Linting chart "clickhouse-monitoring => (version: \"0.1.3\", path: \"clickhouse-monitoring\")"
>>> yamale --schema /opt/hostedtoolcache/ct/3.14.0/amd64/etc/chart_schema.yaml clickhouse-monitoring/Chart.yaml
Validating clickhouse-monitoring/Chart.yaml...
Validation success! 👍
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/Chart.yaml
>>> yamllint --config-file /opt/hostedtoolcache/ct/3.14.0/amd64/etc/lintconf.yaml clickhouse-monitoring/values.yaml
Validating maintainers...
>>> git ls-remote --get-url origin
>>> helm lint clickhouse-monitoring
==> Linting clickhouse-monitoring
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

------------------------------------------------------------------------------------------------------------------------
✔︎ clickhouse-monitoring => (version: "0.1.3", path: "clickhouse-monitoring")
------------------------------------------------------------------------------------------------------------------------
All charts linted successfully

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

Testing chart result

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 cc941978cae3b374acfffb16289baa675e62d692 -- amundsen applause-btn clickhouse-keeper clickhouse-monitoring commento gaxy hermes-agent pgbouncer scheduling-restart spark-shuffle-service uptime-kuma zeppelin
Directory "clickhouse-monitoring" is not a valid chart directory. Skipping...

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
All charts installed successfully

renovate Bot force-pushed the renovate/alpine-curl-8.x branch from 55ac309 to e8bc7ff Compare September 18, 2026 16:12

renovate Bot force-pushed the renovate/alpine-curl-8.x branch from e8bc7ff to 6969464 Compare September 25, 2026 00:52

Update alpine/curl Docker tag to v8.23.0

8366fb5

renovate Bot changed the title ~~Update alpine/curl Docker tag to v8.22.0~~ Update alpine/curl Docker tag to v8.23.0 Oct 31, 2026

renovate Bot force-pushed the renovate/alpine-curl-8.x branch from 6969464 to 8366fb5 Compare October 31, 2026 04:28

Conversation

renovate Bot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Configuration

Uh oh!

duyetbot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

duyetbot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Sep 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duyetbot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Sep 5, 2026 •

edited

Loading

duyetbot commented Sep 5, 2026 •

edited

Loading

duyetbot commented Sep 5, 2026 •

edited

Loading

duyetbot commented Sep 5, 2026 •

edited

Loading

duyetbot commented Sep 5, 2026 •

edited

Loading

duyetbot commented Sep 5, 2026 •

edited

Loading

coderabbitai Bot commented Sep 18, 2026 •

edited

Loading

duyetbot commented Sep 18, 2026 •

edited

Loading

duyetbot commented Sep 18, 2026 •

edited

Loading

duyetbot commented Sep 18, 2026 •

edited

Loading

duyetbot commented Sep 18, 2026 •

edited

Loading

duyetbot commented Sep 18, 2026 •

edited

Loading

duyetbot commented Sep 25, 2026 •

edited

Loading

duyetbot commented Sep 25, 2026 •

edited

Loading

duyetbot commented Sep 25, 2026 •

edited

Loading

duyetbot commented Sep 25, 2026 •

edited

Loading

duyetbot commented Sep 25, 2026 •

edited

Loading

duyetbot commented Oct 31, 2026 •

edited

Loading

duyetbot commented Oct 31, 2026 •

edited

Loading

duyetbot commented Oct 31, 2026 •

edited

Loading

duyetbot commented Oct 31, 2026 •

edited

Loading

duyetbot commented Oct 31, 2026 •

edited

Loading