komodorio / helm-charts Goto Github PK

in the k8s-watcher it says that the default value for the image.pullPolicy is always but the default value (according to the values.yaml) is different

Hi all!

When utilising helm-dashboard, version 0.1.2, a superfluous rule is added to the ClusterRole upon creation, when the dashboard.allowWriteActions value is set to true. This is the default behaviour.

Although not a bug as such, and the ClusterRole works as required, it is not very aesthetically pleasing / clean.

In the example below, the first item in the rule array is unnecessary:

ClusterRole (rbac.authorization.k8s.io) has been added:
-
+ # Source: helm-dashboard/templates/serviceaccount.yaml
+ kind: ClusterRole
+ apiVersion: rbac.authorization.k8s.io/v1
+ metadata:
+   name: dashboard-helm-dashboard
+ rules:
+   - apiGroups: ["*"]
+     resources: ["*"]
+     verbs: ["get", "list", "watch"]
+   - apiGroups: ["*"]
+     resources: ["*"]
+     verbs: ["get", "list", "watch", "create", "delete", "patch", "update"]

Thanks for reading.

Hey everyone, I am trying to play with komodor

I tried to run command from welcome window: helm repo add komodorio https://helm-charts.komodor.io ; helm repo update; helm upgrade --install k8s-watcher komodorio/k8s-watcher --set watcher.actions.basic=true --set watcher.actions.advanced=true --set watcher.actions.podExec=true --set metrics.enabled=true --set apiKey=xxx --set watcher.clusterName=default --wait --timeout=90s && open https://app.komodor.com/main/services

I have created komodor namespace as prerequisite

Seems like something went wrong:

Namespace "komodor" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "k8s-watcher"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "komodor"

I use helm 3.10.1

Since action/checkout@v2 uses Node 12.x.x and it is deprecated I think we must use action/checkout@v3

I am trying to redact logs and below is what I am using from the documentation here

    logs:
      namespaceDenylist: ["kube-system"]
      redact:
        - "password=(.+?)\b"
        - "(?U)\"sessionId\": (\".+\"{1})"

This gives me the error :

Error: INSTALLATION FAILED: YAML parse error on komodor-agent/templates/configmap.yaml: error converting YAML to JSON: yaml: control characters are not allowed

any suggestions?

Hi,
As i mentioned in title, i want to keep my helm-dashboard data . so i enable the persistence option and set the storageClass name.
But the the result is
persistentvolume-controller no persistent volumes available for this claim and no storage class is set
here is the part of my value setting:
` dashboard:
allowWriteActions: true
persistence:
enabled: true

## If defined, storageClassName: <storageClass>
## If set to "-", storageClassName: "", which disables dynamic provisioning
## If undefined (the default) or set to null, no storageClassName spec is
##   set, choosing the default provisioner.  (gp2 on AWS, standard on
##   GKE, AWS & OpenStack)
##
storageClass: "openebs-hostpath"

## Helm Dashboard Persistent Volume access modes
## Must match those of existing PV or dynamic provisioner
## Ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
##
accessModes:
  - ReadWriteOnce

## Helm Dashboard Persistent Volume labels
##
labels: {}

## Helm Dashboard Persistent Volume annotations
##
annotations: {}

## Set path in case you want to use local host path volumes (not recommended in production)
##
hostPath: ""

## Helm Dashboard data Persistent Volume size
##
size: 1024M`

Btw, i checked the pvc.yaml in templates, found the value "storageClassName" no mapping , wonder if there is any possibilities is related with this part?

I installed the helm-dashboard using the helm chart described here: https://github.com/komodorio/helm-charts/tree/master/charts/helm-dashboard

Unfortunately I do not see any Installed charts:

There are many of them on the cluster which is running helm-dashboard:

❯ helm ls -A                                                                                                                                                       ⎈ mgmt01
NAME                    	NAMESPACE                	REVISION	UPDATED                                	STATUS  	CHART                                                                                   	APP VERSION
aws-ebs-csi-driver      	aws-ebs-csi-driver       	1       	2023-02-16 05:03:57.450296564 +0000 UTC	deployed	aws-ebs-csi-driver-2.17.0                                                               	1.16.0
cert-manager            	cert-manager             	1       	2023-02-16 05:06:25.522097992 +0000 UTC	deployed	cert-manager-v1.11.0                                                                    	v1.11.0
cnpg                    	cnpg-system              	1       	2023-02-16 05:06:55.508180141 +0000 UTC	deployed	cloudnative-pg-0.17.0                                                                   	1.19.0
crossplane              	crossplane-system        	1       	2023-02-16 05:02:28.862560764 +0000 UTC	deployed	crossplane-1.11.0                                                                       	1.11.0
dex                     	dex                      	1       	2023-02-16 05:10:14.121739678 +0000 UTC	deployed	dex-0.13.0                                                                              	2.35.3
external-dns            	external-dns             	1       	2023-02-16 05:07:22.217294821 +0000 UTC	deployed	external-dns-6.13.3

There are no other details in the logs:

❯ kubectl logs -n helm-dashboard helm-dashboard-f94df8567-s6wqq
time="2023-02-16T05:03:23Z" level=info msg="Helm Dashboard by Komodor, version 1.0.0 (none @ unknown)"
time="2023-02-16T05:03:23Z" level=info msg="Got no kubectl config contexts, will attempt to detect if we're inside cluster..."
time="2023-02-16T05:03:23Z" level=warning msg="Newer Helm Dashboard version is available: v1.1.0"
time="2023-02-16T05:03:23Z" level=warning msg="Upgrade instructions: https://github.com/komodorio/helm-dashboard#installing"
time="2023-02-16T05:03:25Z" level=info msg="Discovered Checkov version: 2.1.244"
time="2023-02-16T05:03:25Z" level=info msg="Discovered Trivy: Version: 0.18.3"
time="2023-02-16T05:03:25Z" level=info msg="User analytics is collected to improve the quality, disable it with --no-analytics"
time="2023-02-16T05:03:25Z" level=info msg="Access web UI at: http://0.0.0.0:8080"
[GIN] 2023/02/16 - 05:03:30 | 200 |     136.831µs |      10.0.1.248 | GET      "/status"
...

I used the following Helm values when installed the helm-dashboard:

dashboard:
  # allowWriteActions: false
  persistence:
    enabled: false
ingress:
  enabled: true
  className: nginx
  annotations:
    forecastle.stakater.com/expose: "true"
    forecastle.stakater.com/icon: "https://raw.githubusercontent.com/komodorio/helm-dashboard/9bb597f366426daa2ada06fb87eee2094e862aa3/pkg/dashboard/static/logo.svg"
    forecastle.stakater.com/appName: Helm Dashboard
    nginx.ingress.kubernetes.io/auth-url: https://oauth2-proxy.${CLUSTER_FQDN}/oauth2/auth
    nginx.ingress.kubernetes.io/auth-signin: https://oauth2-proxy.${CLUSTER_FQDN}/oauth2/start?rd=$scheme://$host$request_uri
  hosts:
    - host: helm-dashboard.${CLUSTER_FQDN}
      paths:
        - path: /
          pathType: ImplementationSpecific
  tls:
    - hosts:
        - helm-dashboard.${CLUSTER_FQDN}

Any ideas why it is not working?

Thank you

Release "komodor-agent" does not exist. Installing it now.
Error: ConfigMap "network-mapper-store-Local" is invalid: metadata.name: Invalid value: "network-mapper-store-Local": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')

for Openshift will it work.
and also if want to add login and password in dashboard how we can add.

Hello, I have seen that every open source projects it gets easier for contributors to get into the community if there are socials in the readme as well, so I would like to add that if it gets approved.
Thank you.

There is a bug in the komodor-agent helm chart in

Should be fixed to resources: {{ toYaml .Values.components.komodorAgent.supervisor.resources | trim | nindent 4 }}