Why pods are not showing in Deployments

[enter-marlah]

Ask a question

I have built and deployed a test automation. The deployed automation is running in Kubernetes and everything works but the deployment is not showing up in Karavan UI. Should I have something in Containers : No Pods in below image? Thanks!

Variant

Web Application

Container Management (if applicable)

Kubernetes

Operating System (if applicable)

None

Version

4.10.2

[mgubaidullin]

Check if Karavan service account has sufficient privileges (roles) in k8s

[enter-marlah]

We have the normal karavan service account created with the roles and bindings from the Karavan install yaml-files. We use a different service account in our deployment.jkube.yaml that has the same roles and bindings as the Karavan service account.

Does this cause the problem?

[edubencz]

Any solution to this problem of No Pods?

I can see karavan web app probing GET 'ui/container' endpoint, and my integration container/pod is visible in the response list.

I imagine there is some configuration I may be missing, but I cant find any information....

I've already set 3 different serviceAccounts, one for dev mode, another for builder and one just for the integration services. All configured with the roles and access sugested in K8s files in installation docs.

I have no errors in Karavan container logs (eg: as of unauthorized)

[edubencz]

Looking at the frontend code, it seems to require pods to have an specific 'type' to be 'packaged' but my pods are getting tyoe 'unkown':

[edubencz]

It seems to me that my build step is not applying the expected label to identify the pod type?

LABEL_TYPE = "org.apache.camel.karavan/type";

If I access the pod manually via k8, and apply this label, it doesn't seem to have any effect.

I'm using the default k8 object settings from the Kubernetes template installation.

[mgubaidullin]

Pod should have label "org.apache.camel.karavan/type"="project" for Karavan 4.10.x and below.
Usually configured in build.sh

...
-Djib.container.labels=org.apache.camel.karavan/type=project,org.apache.camel.karavan/projectId=$PROJECT_ID \

[mgubaidullin]

packaged will be used in the next version

[edubencz]

Perfect! thanks @mgubaidullin, that solved the problem!

One more thing. The button Deploy is enabled, and if I click it, an error toast pops up, and the request details show some problem trying to find a file: "Resource file kubernetes.yaml not found"

[mvolf]

@edubencz Did you get any reply or progress on this issue? I found that the deploy endpoint is looking for a "kubernetes.yaml" file inside of the project that the user is trying to deploy, however this file doesn't exist obviously.
There are also absolutely no signs of this file, apart from this reference in the deploy EP. I tried searching Karavan github issues/discussions but wound nothing except of this issue :)

[mgubaidullin]

You do not need explicitly deploy application to k8s.
Build script makes it for you k8s:apply.

camel-karavan/karavan-app/src/main/resources/configuration/kubernetes/build.sh

Line 18 in 2a8f3d0

mvn package jib:build k8s:resource k8s:apply \

[mvolf]

@mgubaidullin Thanks for the reply, I'm aware of this. I still believe that the Deploy button should then either be hidden for k8s, or the kubernetes.yaml mandatory file should be provided.

[mgubaidullin]

Deploy button should be hidden for k8s It was implemented like this, however some users asked to have custom kubernetes.yaml for deployment. I will add verification to show this button only if kubernetes.yaml exists

[mvolf]

That would be great, thanks @mgubaidullin. Where can we see an example of this kubernetes.yaml file if we want to incorporate it?

[mgubaidullin]

kubernetes.txt

[mgubaidullin]

#1541