stable/docs/getting-started/lifecycle-management/

[giscus[bot]]

stable/docs/getting-started/lifecycle-management/

Achieve cloud-native application lifecycle orchestration with Keptn. Enhance Kubernetes monitoring, streamline metrics ingestion, and automate deployment validation. Join the Keptn community for insights.

https://keptn.sh/stable/docs/getting-started/lifecycle-management/

[bakaibalazs]

Hello! I was following this tutorial; almost everything works well, however, the Keptn job re-executes every 5 minutes, and recreating the task again and again. It should only execute once.
When I check the keptntasks.lifecycle.keptn.sh, the status is 'Progressing'. Could you please help me understand what the problem could be? Thanks for your help!

[odubajDT]

Thank you for the info! I was trying to reproduce the problem using my local kind cluster, but it worked without issues. I applied the resources you posted:

• namespace
• keptnTask
• KeptnTaskDefinition

The KeptnTask succeeded in few seconds and was not reconciled anymore

Afterwards (after 5 min) I applied:

• KeptnAppContext
• Deployment
• Service

Also went without issues. Also in the logs I didn't see anything suspicious. What version of Keptn are you please using?

You are saying you are using kubeadm. Maybe there is some local config which is breaking the functionality? Not familiar with this that much.

Can you maybe try the steps described again with a new cluster? Let's see if you can reproduce it again

Thank you!

[bakaibalazs]

Hello!
I installed the latest Keptn (keptn-0.8.0; v2.2.0) via HELM.

I tested it with the Killercoda Kubernetes v1.31.0 sandbox environment (https://killercoda.com/playgrounds/scenario/kubernetes), and the issue occurred there as well.

Just to give it a try, I also tested it with Rancher RKE2 (v1.30.5+rke2r1), and luckily it worked well.

So, I believe it may be a compatibility issue with the clean kubeadm installation on Kubernetes v1.31.0.
Based on the Kubernetes documentation, kubeadm is the official tool to install vanilla Kubernetes.
What do you think the problem could be?

[odubajDT]

Hello, thank for the answer. Not sure where the problem is, but it does seem like a compatibility issue. I will try to investigate it further during the next week and will keep you updated!

[odubajDT]

Hello! We have managed to find the issue. It seems like the jobs/task logic handling was not compatible with the latest job updates in k8s. Until now we are only support k8s versions until 1.29. We are already working on a fix, which will be part of the next release.

Issue with description of the problem present here

Thank you for reporting the issue!

[bakaibalazs]

Hello! Thanks for the update! You're welcome!

[odubajDT]

Closing this discussion, as the problem is clear and will be resolved