Issue with install and uninstall using helm

[umgbhalla]

What did you do? Unnstalled tobs using helm

Environment EKS, with kubernetes 1.22

• tobs version: 0.10.1

  tobs version

• Kubernetes version information: 1.22

  kubectl version

• Kubernetes cluster kind: eks

Why on helm delete tobs are these deployment/services not deleted ? is this supposed to happen ?

[nhudson]

This is a known issue, described in #365. It's due to some limitations with Helm that we currently do not have a fix for. For now if you want to completely remove the installation, the best method is to delete the namespace you installed it to.

[umgbhalla]

after removing this completly , and doing a tobs install with cli this happens

with helm upgrade --install tobs timescale/tobs --version 0.10.1

[nhudson]

@umgbhalla can you try it with the latest release of tobs? v12.0.0

The CLI is considered deprecated as well. I would also suggest installing to a specific namespace for the tobs stack if you can.

[siva-kubikk]

@nhudson I ran into the same issue as well when trying to install with tobs. If the tobs cli is deprecated, what is the best way to install tobs that can be easily automated and added as part of a CI/CD pipeline?

$ tobs install -y --version '12.0.0'
cert-manager version v1.6.1 exists in the cluster, skipping the installation...
Error: could not install The Observability Stack: failed to find the value from the keys in values.yaml [promscale openTelemetry enabled]

[nhudson]

@siva-kubikk the CLI is deprecated with the latest version of tobs (via #471). The only way to install it is with Helm right now.

[siva-kubikk]

@nhudson Got it.

[umgbhalla]

@nhudson , helm install in a new namespace definitely worked , i was wondering if i can install 12.0.0 on eks (which is on k8s 1.22)

[nhudson]

@umgbhalla great to hear! As for supporting Kubernetes 1.22.x, it hasn't been tested with that old over a version. I would say for sure it will work with 1.23 & 1.24 for sure. I would suspect that there will be some compatibility issues, but like I said it hasn't been tested.

[github-actions[bot]]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[github-actions[bot]]

This issue was closed because it has been stalled for 30 days with no activity.