helm install fail

[NiceMattHui]

helm version version.BuildInfo{Version:"v3.5.4"

[engnatha]

The values documentation doesn't make any mention of this, but I went looking at the helper definitions and got a working helm chart install that makes it beyond this error.

serviceAccount:
  create: true
tap:
  docker:
    tag: v51.0.0

If you do this, you can run

helm install --version 51.0.0 -f <path/to/values.yaml> kubeshark kubeshark/kubeshark

Here's what I see when getting through that deployment

NAME: kubeshark
LAST DEPLOYED: Thu Oct 19 18:04:53 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for installing Kubeshark.

Registry: docker.io/kubeshark
Tag: v51.0.0

Your deployment has been successful. The release is named `kubeshark` and it has been deployed in the `default` namespace.
Notice: Telemetry is enabled. Kubeshark will collect anonymous usage statistics.

To access the application, follow these steps:

1. Perform port forwarding with the following commands:

    kubectl port-forward -n default service/kubeshark-front 8899:80

2. Once port forwarding is done, you can access the application by visiting the following URL in your web browser:
    http://0.0.0.0:8899

[NiceMattHui]

@engnatha
Encountered a new error during startup:
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRoleBinding "kubeshark-cluster-role-binding" 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 "kubeshark"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"

The content of /home/sysadmin/.kubeshark/values.yaml:

[engnatha]

Hard to say, but you might be best to helm uninstall your kubeshark and then delete anything related to a prior install.

[maxlaverse]

Had the same issue @NiceMattHui, and helm uninstall or kuebshark clean didn't work because most of the resources were already gone. The second line of your error message tells you which resource is conflicting. Delete them until you don't get any error anymore. According to the message, you should start with kubectl delete clusterrolebinding kubeshark-cluster-role-binding

[mertyildiran]

Should be fixed with bed59e1