helm install --values https://umh.app/development....
# umh-support
a
helm install --values https://umh.app/development.yaml united-manufacturing-hub .\deployment\united-manufacturing-hub\ -n united-manufacturing-hub Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "united-manufacturing-hub-grafana" namespace: "" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "united-manufacturing-hub-grafana" namespace: "united-manufacturing-hub" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "united-manufacturing-hub-vernemq" namespace: "united-manufacturing-hub" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1" ensure CRDs are installed first]
j
really? can you check the version of minikube?
what version are you running?
ah look at the post of magoon2020
he also used an older versaion
same error message
a
minikube version: v1.27.1 helm version: v3.10.0 kubectl version: 1.25
I also tried with minikube v1.26.1 same error is coming
n
@Jermuk Same error using https://united-manufacturing-hub.notion.site/Local-minikube-installation-9fec99d665794ef3aa94f0dd5bf23d49 minikube version: v1.27.1 helm version: v3.10.1 kubectl version: 1.25.2
j
would one of you be available for a call? we are really trying to reproduce this error, but struggle so. we've tested it on multiple computer already, but there must be something different
have you installed minikube using choco or something else?
I just saw that @akashtalole problem was solved: https://github.com/united-manufacturing-hub/united-manufacturing-hub/issues/1317 Do you remember what you did?
n
@Jermuk tried reaching you, have notes of what I did, nothing conclusive on #1317 yet. Installed on Ubuntu 22.04.
j
He wrote what he did. He actually downgraded kubernetes. Maybe there are problems with too old versions, but also to new versions
We'll take a look whether we can reproduce the error on a newer version
n
@Jermuk curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 sudo install minikube-linux-amd64 /usr/local/bin/minikube minikube start --driver=docker --cpus 2 --memory 4096 minikube kubectl -- get po -A vi $HOME/.bashrc alias kubectl="minikube kubectl --" . $HOME/.bashrc minikube config set driver docker kubectl create namespace united-manufacturing-hub helm repo add united-manufacturing-hub https://repo.umh.app/ helm repo update
I could try to isolate the problem in or outside of the UMH stack. Is there a link for minikube on TimescaleDB without UMH? https://github.com/timescale/helm-charts/issues/363
Single-node would be nice...
j
ahh that command helps. when you do it like this, you will get a newer minikube version than you would get using using choco. therefore you will get a newer kubernetes version, which explains why we struggled to replciate this issue
it has nothing to do with timescale. it works out of the box once you are using the same version as we
can you try to delete the current minikube cluster, then install minikube v1.26.1 and then try again?
yesss, finally able to replicate it
preparing the commands to make it work now
magic command:
minikube delete && curl -LO https://storage.googleapis.com/minikube/releases/v1.26.1/minikube-linux-amd64 && sudo install minikube-linux-amd64 /usr/local/bin/minikube
@nviz5302 @akashtalole thank you for your patience and help. We will add a note to the tutorial saying that currently only v1.26.1 is supported and that if you want to not use choco, that you can use the following command to install minikube on Ubuntu:
Copy code
curl -LO https://storage.googleapis.com/minikube/releases/v1.26.1/minikube-linux-amd64 && sudo install minikube-linux-amd64 /usr/local/bin/minikube
@pmelichar.
n
@Jermuk thanks a lot. Will try when I get a chance and status you.
@Jermuk 1.26.1 did it. I now have UMH (through step10, then over to MQTT Simulator), Node-RED and my PoC running in parallel! 🤩 (skip 11 through "Enable minikube ingress" since Node-RED running already?) I imported the template, deployed and Node-RED comes up "connecting" for both IoTSensors raw data and IoTSensors contextualized data. Is 0.10.0 expected to be out soon (@Ferdinand from Oct 5th)? It's the ISA95 work I want to look at, but what do you recommend as next steps to get there?
f
@nviz5302 We had to reschedule a bit, so there will be a 0.9.7 (released this week) before 0.10.0. I expect 0.10.0 to be in-testing by end of next week (if you like you can then try the prereleases) and released 1 week afterwards.
5 Views