DaspawnW/vault-crd

Unable to run application on Kubernetes 1.22.2

Closed this issue · 1 comments

Im trying to deploy vault-crd to a new kubernetes cluster with version 1.22.2

I follow the guide at https://vault.koudingspawn.de/install-vault-crd#static-vault-token but when I deploy the rbac.yml to kubernetes the application gets stuck in CrashLooBackOff mode with the error:


  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.2.4.RELEASE)

2021-10-25 15:34:15.950  INFO 1 --- [           main] de.koudingspawn.vault.VaultApplication   : Starting VaultApplication v0.0.1-SNAPSHOT on vault-crd-5f47d4cf75-k9tx6 with PID 1 (/opt/vault-crd.jar started by root in /)
2021-10-25 15:34:15.954  INFO 1 --- [           main] de.koudingspawn.vault.VaultApplication   : No active profile set, falling back to default profiles: default
2021-10-25 15:34:17.615  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2021-10-25 15:34:17.630  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2021-10-25 15:34:17.630  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.30]
2021-10-25 15:34:17.700  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2021-10-25 15:34:17.700  INFO 1 --- [           main] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 1689 ms
2021-10-25 15:34:18.081  INFO 1 --- [           main] o.s.s.c.ThreadPoolTaskScheduler          : Initializing ExecutorService 'vaultThreadPoolTaskScheduler'
2021-10-25 15:34:18.916 ERROR 1 --- [           main] d.k.v.kubernetes.KubernetesConnection    : Please first apply custom resource definition and then restart vault-crd

Have also tried to manually deploy the CRD before running rbac.yml as well without success.

I have validated that the crd is in fact deployed and that the clusterrole has access to it.

kubectl get crd vault.koudingspawn.de
NAME                    CREATED AT
vault.koudingspawn.de   2021-10-25T15:33:16Z
kubectl auth can-i get customresourcedefinitions --as system:serviceaccount:vault-crd:vault-crd-serviceaccount
yes

Hi @ventris,

Please see release 1.8.0 which adds support for Kubernetes 1.22.