We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I deployed Kroki in my K8s cluster as a Helm chart via ArgoCD:
Name: kroki Kind: Application Spec: Source: Chart: kroki Helm: Values Object: Autoscaling: Hpa: Enabled: true Max Replicas: 3 Min Replicas: 1 Ingress: Annotations: acme.cert-manager.io/http01-ingress-class: nginx nginx.ingress.kubernetes.io/force-ssl-redirect: true Enabled: true Hosts: Host: kroki.example.com Paths: / Ingress Class Name: nginx Path Type: Prefix Tls: Hosts: kroki.example.com Secret Name: ingress-kroki-cert Resources: Limits: Cpu: 100m Memory: 250Mi Requests: Cpu: 50m Memory: 100Mi Repo URL: https://cowboysysop.github.io/charts/ Target Revision: 5.3.0 Sync Policy: Automated: Self Heal: true Sync Options: CreateNamespace=true
Unfortunately the kroki pod run into errors :(
{ "timestamp": "1727332329515", "level": "ERROR", "thread": "vert.x-eventloop-thread-0", "logger": "io.vertx.core.impl.launcher.commands.VertxIsolatedDeployer", "message": "Failed in deploying verticle", "context": "default", "exception": " java.lang.IllegalStateException: cacheDir has been removed. FileResolver is closing? -> io.vertx.core.file.impl.FileCache.getCacheDir(FileCache.java:226) -> io.vertx.core.file.impl.FileCache.getFile(FileCache.java:145) -> io.vertx.core.file.impl.FileCache.getCanonicalFile(FileCache.java:153) -> io.vertx.core.file.impl.FileResolverImpl.resolveFile(FileResolverImpl.java:131) -> io.vertx.core.impl.VertxImpl.resolveFile(VertxImpl.java:929) -> io.vertx.core.file.impl.FileSystemImpl$16.perform(FileSystemImpl.java:1066) -> io.vertx.core.file.impl.FileSystemImpl$16.perform(FileSystemImpl.java:1063) -> io.vertx.core.file.impl.FileSystemImpl.readFileBlocking(FileSystemImpl.java:418) -> io.kroki.server.service.HelloHandler.<init>(HelloHandler.java:19) -> io.kroki.server.Server.start(Server.java:150) -> io.kroki.server.Server.lambda$start$1(Server.java:48) -> io.vertx.core.impl.future.FutureImpl$4.onSuccess(FutureImpl.java:176) -> io.vertx.core.impl.future.FutureBase.emitSuccess(FutureBase.java:66) -> io.vertx.core.impl.future.FutureImpl.addListener(FutureImpl.java:231) -> io.vertx.core.impl.future.FutureImpl.onComplete(FutureImpl.java:199) -> io.vertx.config.impl.ConfigRetrieverImpl.getConfig(ConfigRetrieverImpl.java:175) -> io.kroki.server.Server.start(Server.java:44) -> io.vertx.core.impl.DeploymentManager.lambda$doDeploy$5(DeploymentManager.java:210) -> io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:276) -> io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:258) -> io.vertx.core.impl.ContextInternal.lambda$runOnContext$0(ContextInternal.java:56) -> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173) -> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166) -> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) -> io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) -> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) -> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) -> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) -> java.base/java.lang.Thread.run(Unknown Source) " }
Any idea what is missing in this configuration?
If I deploy 5.1.0 (0.24.1) it works fine.
Thanks in advance
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I deployed Kroki in my K8s cluster as a Helm chart via ArgoCD:
Unfortunately the kroki pod run into errors :(
Any idea what is missing in this configuration?
If I deploy 5.1.0 (0.24.1) it works fine.
Thanks in advance
The text was updated successfully, but these errors were encountered: