Kubernetes deployment login credentials

F

FFO•10/17/22, 7:18 AM

Hi - There

Let me quickly verify this. Did you configure something additional (like the externaldomain)?

F

FFO•10/17/22, 11:08 AM

@Elio can you look into this

F

FFO•10/17/22, 11:08 AM

You have the most experience with the helm chart

E

Elio•10/17/22, 11:28 AM

Yes

F

FFO•10/17/22, 12:58 PM

On a sidenote @Elio we have an issue with newer k8s versions

F

FFO•10/17/22, 12:59 PM

1.25 at least throws errors

F

FFO•10/17/22, 12:59 PM

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "crdb-budget" namespace: "zitadel" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer-client" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first]

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "crdb-budget" namespace: "zitadel" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer-client" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first]

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "crdb-budget" namespace: "zitadel" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer-client" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first]

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "crdb-budget" namespace: "zitadel" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "crdb-rotate-self-signer-client" namespace: "zitadel" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first]

E

Elio•10/17/22, 1:22 PM

Good to know

E

Elio•10/17/22, 1:23 PM

I'll create an issue for that

E

Elio•10/17/22, 1:26 PM

@Jeeth_JJ with which k8s version should I try to reproduce your issue?

E

Elio•10/17/22, 1:49 PM

hm, how could you install ZITADEL in the first place then?

I'll try it too, today.

JJeeth_JJ @FFO The issue you mentioned is because of using a deprecated api version. Can ...

F

FFO•10/17/22, 7:48 PM

ah yes i am aware of that

but it breaks our easy to start process so we need to fix it ASAP

E

Elio•10/18/22, 7:48 AM

I'm on it

E

Elio•10/18/22, 9:42 AM

@Jeeth_JJ A new chart version with the updated cockroach chart dependency that supports k8s 1.25 was just released. With the latest zitadel chart, I couldn't reproduce the issue using the following commands.

helm repo update zitadel

kind create cluster --image kindest/node:v1.25.0

helm install --namespace zitadel --create-namespace my-zitadel zitadel/zitadel --set zitadel.masterkey="MasterkeyNeedsToHave32Characters"   --set zitadel.configmapConfig.ExternalSecure=false   --set zitadel.configmapConfig.TLS.Enabled=false   --set zitadel.secretConfig.Database.cockroach.User.Password="a-zitadel-db-user-password"   --set replicaCount=1   --set cockroachdb.single-node=true   --set cockroachdb.statefulset.replicas=1

kubectl -n zitadel port-forward svc/my-zitadel 8080

helm repo update zitadel

kind create cluster --image kindest/node:v1.25.0

helm install --namespace zitadel --create-namespace my-zitadel zitadel/zitadel --set zitadel.masterkey="MasterkeyNeedsToHave32Characters"   --set zitadel.configmapConfig.ExternalSecure=false   --set zitadel.configmapConfig.TLS.Enabled=false   --set zitadel.secretConfig.Database.cockroach.User.Password="a-zitadel-db-user-password"   --set replicaCount=1   --set cockroachdb.single-node=true   --set cockroachdb.statefulset.replicas=1

kubectl -n zitadel port-forward svc/my-zitadel 8080

helm repo update zitadel

kind create cluster --image kindest/node:v1.25.0

helm install --namespace zitadel --create-namespace my-zitadel zitadel/zitadel --set zitadel.masterkey="MasterkeyNeedsToHave32Characters"   --set zitadel.configmapConfig.ExternalSecure=false   --set zitadel.configmapConfig.TLS.Enabled=false   --set zitadel.secretConfig.Database.cockroach.User.Password="a-zitadel-db-user-password"   --set replicaCount=1   --set cockroachdb.single-node=true   --set cockroachdb.statefulset.replicas=1

kubectl -n zitadel port-forward svc/my-zitadel 8080

helm repo update zitadel

kind create cluster --image kindest/node:v1.25.0

helm install --namespace zitadel --create-namespace my-zitadel zitadel/zitadel --set zitadel.masterkey="MasterkeyNeedsToHave32Characters"   --set zitadel.configmapConfig.ExternalSecure=false   --set zitadel.configmapConfig.TLS.Enabled=false   --set zitadel.secretConfig.Database.cockroach.User.Password="a-zitadel-db-user-password"   --set replicaCount=1   --set cockroachdb.single-node=true   --set cockroachdb.statefulset.replicas=1

kubectl -n zitadel port-forward svc/my-zitadel 8080

Then I can log in with zitadel-admin@zitadel.localhost and Password1!

F

FFO•10/18/22, 9:45 AM

works on docker for windows as well