DaspawnW/vault-crd

Vault-crd helm : vault-crd pod restarts with error "main] d.k.v.kubernetes.KubernetesConnection : Please first apply custom resource definition and then restart vault-crd"

Closed this issue · 2 comments

Hi,
I am installing vault-crd using helm charts (version: 1.6.3) but after deploying vault-crd pod restarts with below error : -
. ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _ | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
' |
| .__|| ||| |_, | / / / /
=========||==============|/=///_/
:: Spring Boot :: (v2.2.4.RELEASE)

2023-01-24 09:29:01.280 INFO 1 --- [ main] de.koudingspawn.vault.VaultApplication : Starting VaultApplication v0.0.1-SNAPSHOT on vault-crd-6589b6c7bd-v4hdq with PID 1 (/opt/vault-crd.jar started by root in /)
2023-01-24 09:29:01.284 INFO 1 --- [ main] de.koudingspawn.vault.VaultApplication : No active profile set, falling back to default profiles: default
2023-01-24 09:29:02.950 INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2023-01-24 09:29:02.965 INFO 1 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2023-01-24 09:29:02.965 INFO 1 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.30]
2023-01-24 09:29:03.035 INFO 1 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2023-01-24 09:29:03.035 INFO 1 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 1688 ms
2023-01-24 09:29:03.439 INFO 1 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Initializing ExecutorService 'vaultThreadPoolTaskScheduler'
2023-01-24 09:29:04.245 ERROR 1 --- [ main] d.k.v.kubernetes.KubernetesConnection : Please first apply custom resource definition and then restart vault-crd
`

Hi @anupy023 ,

Could you pls give me some hint what Kubernetes Version you have running?
To doublecheck, you have the custom resource definition already applied?

When I check the output it seems like you use an old version of Vault-CRD; the Spring Boot v2.2.4 is quiet old. Maybe you can try to use 1.11.0 of Vault-CRD.

As there is no further feedback I would close the ticket.