diff --git a/.github/actions/spelling/expect.txt b/.github/actions/spelling/expect.txt
index 4fcf68b371..98e0d8be85 100644
--- a/.github/actions/spelling/expect.txt
+++ b/.github/actions/spelling/expect.txt
@@ -382,7 +382,6 @@ kwds
 kwi
 kwv
 kyverno
-lastmod
 lastword
 Lato
 LFC
diff --git a/docs/blog/posts/argocd-keptn-health.md b/docs/blog/posts/argocd-keptn-health.md
new file mode 100644
index 0000000000..ea70bc22b2
--- /dev/null
+++ b/docs/blog/posts/argocd-keptn-health.md
@@ -0,0 +1,183 @@
+---
+date: 2024-05-15
+authors: [odubajDT]
+description: >
+  This blog post presents how Keptn can show application health when integrated with ArgoCD.
+categories:
+  - ArgoCD
+  - Application health
+comments: true
+---
+
+# Application health checks with Keptn using ArgoCD
+
+In this blog post we will present a planned Keptn and
+[ArgoCD](https://argo-cd.readthedocs.io/en/stable/) integration to execute
+advanced application health checks using Keptn.
+
+Keptn provides an effective way to perform application health checks using the
+pre- or post-deployment [tasks](https://keptn.sh/stable/docs/guides/tasks/)
+and [evaluations](https://keptn.sh/stable/docs/guides/evaluations/).
+ArgoCD application health checks evaluate whether the application is successfully deployed
+and the workloads are running on the cluster
+but they do not show if the services
+of a single application are actually working as expected.
+For example, it could be the case that the individual services deployed by ArgoCD are up and
+running, but due to a slow `response time` (let's say `3s`), the users would have a bad experience.
+Keptn pre- and post-deployment tasks and evaluations complement the missing functionality
+by providing a straight-forward way to examine the application's ability to perform
+the actions for which it was developed.
+In this particular case, Keptn can perform `KeptnEvaluations` to examine whether the `response time`
+of the application services are in the expected boundaries.
+
+<!-- more -->
+
+## How it's going to work?
+
+Keptn and ArgoCD need to be installed and enabled on the same
+cluster.
+To install both components, you can follow the
+[Keptn installation instructions](https://keptn.sh/stable/docs/installation/)
+and
+[ArgoCD installation instructions](https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/).
+The reason is that we want to have ArgoCD perform the actual deployment
+of the application and Keptn execute the advanced application health checks.
+
+Additionally, we will need to have an ArgoCD extension, which consists of
+a React application extending the ArgoCD UI, implemented as  an
+[ArgoCD UI Application Tab Extension](https://argo-cd.readthedocs.io/en/stable/developer-guide/extensions/ui-extensions/#application-tab-extensions)
+and a
+[ArgoCD proxy extension](https://argo-cd.readthedocs.io/en/stable/developer-guide/extensions/proxy-extensions/)
+allowing Keptn (which will work as a backend service)
+to push the application health status data to the ArgoCD UI.
+
+## What's the added value of Keptn?
+
+Let's try to show a real-life example of an application deployed via ArgoCD,
+which has a healthy green status in ArgoCD UI, but it's not working as expected
+due to a slow `response time` of the application.
+
+We will deploy a simple [podtato-head](https://github.com/podtato-head/podtato-head)
+application via ArgoCD, which consists of multiple Deployments and Services.
+The Argo Application deploying the manifests can look like the following:
+
+```yaml
+{% include "./argocd-keptn-health/argo-app.yaml" %}
+```
+
+After a few moments, the `podtato-head` application is successfully deployed and all pods
+are running.
+
+![Running Pods](./argocd-keptn-health/running-pods.png)
+
+We can also examine the ArgoCD UI and everything seems to be working as expected and the
+`podtato-head` application is healthy.
+
+![Healthy App](./argocd-keptn-health/healthy-app.png)
+
+Let's now try to add some health checks of the `podtato-head` application
+and use Keptn to execute them.
+For this, we are going to use the
+[Keptn Release Lifecycle Management](https://keptn.sh/stable/docs/getting-started/lifecycle-management/)
+feature and perform the checks via `KeptnEvaluations`.
+
+Apart from `KeptnEvaluations`, `KeptnTasks` can be used to execute health checks
+of an application as well, for example performing an HTTP request to test
+the reachability of a certain service exposed on a configured port.
+
+For simplicity, we assume that you already have a data source
+(such as Prometheus, Dynatrace, or Datadog)
+deployed and configured as a metrics provider on your cluster.
+This data provider can fetch the `response time` values
+of the services.
+In our setup, we are going to use [Prometheus](https://prometheus.io/).
+
+First, we need to create [KeptnMetric](https://keptn.sh/stable/docs/reference/crd-reference/metric/)
+and [KeptnMetricsProvider](https://keptn.sh/stable/docs/reference/crd-reference/metricsprovider/)
+resources in our cluster.
+These two resources contain a simple query for fetching the `response time` of the `podtato-head`
+application service and configuration for the metrics provider supplying the data.
+
+```yaml
+{% include "./argocd-keptn-health/metric.yaml" %}
+```
+
+Next, we add `KeptnEvaluationDefinition` into our git repository, where our
+`podtato-head` application lives.
+It defines the [SLO](https://www.dynatrace.com/news/blog/what-are-slos/)
+by linking the existing `KeptnMetric` resource and providing the rule the value should fullfil.
+
+```yaml
+{% include "./argocd-keptn-health/evaluationdefinition.yaml" %}
+```
+
+Additionally, we annotate the `podtato-head-frontend` Deployment to execute
+the evaluation as part of `post-deployment-evaluation` checks.
+
+```yaml
+{% include "./argocd-keptn-health/annotation.yaml" %}
+```
+
+After these two changes are made in our git repository, ArgoCD will see changes and re-trigger
+the deployment of `podtato-head`.
+Keptn waits until all of the
+application pods are running and then it executes `post-deployment-evaluation` evaluations.
+
+Due to slow `response time` of the `podtato-head-frontend` service, the
+executed `KeptnEvaluation` fails.
+
+Here we see that Keptn lets us perform more advanced health checks
+(tasks or evaluations) and verify that the application deployed via ArgoCD is healthy.
+
+## How to show Keptn health status in ArgoCD UI?
+
+Using Keptn together with ArgoCD brings a lot of value, which we saw in the previous section,
+but observing application health status by inspecting the status of the
+various resources using `kubectl` is not the best user experience.
+The data should be nicely displayed in the ArgoCD UI to provide the user with an overview
+of whether the application was deployed successfully, if it's synchronized, and if it's healthy, all in
+one place.
+
+To implement this, we are going to implement an ArgoCD UI extension with additional application health
+data that are retrieved from Keptn.
+This way, the ArgoCD UI will act as a single source of truth for the user, providing all
+the information about the deployed application.
+
+Below you can see the first mock-ups that show what the ArgoCD UI extension might look like
+and how a failed `KeptnEvaluation` and therefore unhealthy Keptn status of `podtato-head-frontend`
+Deployment might be displayed on the main ArgoCD UI screen.
+
+![Main screen unhealthy](./argocd-keptn-health/main-screen-unhealthy-keptn.png)
+
+Additionally, it should be possible to also examine the details of the unhealthy
+application and potentially see the reason for the failure of the checks.
+
+![Details screen unhealthy](./argocd-keptn-health/details-screen-unhealthy-keptn.png)
+
+## Summary
+
+Time to sum up what we have presented in this blog post.
+We have seen how Keptn can easily complement ArgoCD
+and enhance its functionality by providing more insights into
+application health status.
+We showed an example where ArgoCD wasn't able to detect that
+the deployed application is not healthy and used `KeptnEvaluations`
+for performing more advanced checks.
+In the end, we looked at the first drafts of the potential
+ArgoCD UI extension and how it can easily display the
+`Keptn health status` as part of the standard ArgoCD application
+health status.
+
+We hope that this blog post gives you an idea and some inspiration
+on how these two projects can cooperate and complement each other
+effectively in order to support continuous delivery of applications
+faster and more reliably.
+
+We would really appreciate if you can provide us feedback on this
+feature below in the comments!
+
+## Useful links
+
+- <https://keptn.sh>
+- <https://argo-cd.readthedocs.io/en/stable/>
+- <https://prometheus.io/>
diff --git a/docs/blog/posts/argocd-keptn-health/annotation.yaml b/docs/blog/posts/argocd-keptn-health/annotation.yaml
new file mode 100644
index 0000000000..8aacadf55e
--- /dev/null
+++ b/docs/blog/posts/argocd-keptn-health/annotation.yaml
@@ -0,0 +1,3 @@
+metadata:
+  labels:
+    keptn.sh/post-deployment-evaluations: response-time-evaluation
diff --git a/docs/blog/posts/argocd-keptn-health/argo-app.yaml b/docs/blog/posts/argocd-keptn-health/argo-app.yaml
new file mode 100644
index 0000000000..540d897386
--- /dev/null
+++ b/docs/blog/posts/argocd-keptn-health/argo-app.yaml
@@ -0,0 +1,18 @@
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: podtato-head
+  namespace: argocd
+spec:
+  project: default
+  source:
+    repoURL: https://github.com/keptn-sandbox/keptn-lifecycle-toolkit-examples
+    targetRevision: main
+    path: sample-app/version-2
+  destination:
+    server: https://kubernetes.default.svc
+    namespace: podtato-kubectl
+  syncPolicy:
+    automated:
+      selfHeal: true
+      prune: true
diff --git a/docs/blog/posts/argocd-keptn-health/details-screen-unhealthy-keptn.png b/docs/blog/posts/argocd-keptn-health/details-screen-unhealthy-keptn.png
new file mode 100644
index 0000000000..0870e2e6d7
Binary files /dev/null and b/docs/blog/posts/argocd-keptn-health/details-screen-unhealthy-keptn.png differ
diff --git a/docs/blog/posts/argocd-keptn-health/evaluationdefinition.yaml b/docs/blog/posts/argocd-keptn-health/evaluationdefinition.yaml
new file mode 100644
index 0000000000..c41efba160
--- /dev/null
+++ b/docs/blog/posts/argocd-keptn-health/evaluationdefinition.yaml
@@ -0,0 +1,9 @@
+apiVersion: lifecycle.keptn.sh/v1
+kind: KeptnEvaluationDefinition
+metadata:
+  name: response-time-evaluation
+spec:
+  objectives:
+    - evaluationTarget: "<0.3"
+      keptnMetricRef:
+        name: response-time
diff --git a/docs/blog/posts/argocd-keptn-health/healthy-app.png b/docs/blog/posts/argocd-keptn-health/healthy-app.png
new file mode 100644
index 0000000000..2e2a4d576d
Binary files /dev/null and b/docs/blog/posts/argocd-keptn-health/healthy-app.png differ
diff --git a/docs/blog/posts/argocd-keptn-health/main-screen-unhealthy-keptn.png b/docs/blog/posts/argocd-keptn-health/main-screen-unhealthy-keptn.png
new file mode 100644
index 0000000000..b9286b9924
Binary files /dev/null and b/docs/blog/posts/argocd-keptn-health/main-screen-unhealthy-keptn.png differ
diff --git a/docs/blog/posts/argocd-keptn-health/metric.yaml b/docs/blog/posts/argocd-keptn-health/metric.yaml
new file mode 100644
index 0000000000..bd9308a9cd
--- /dev/null
+++ b/docs/blog/posts/argocd-keptn-health/metric.yaml
@@ -0,0 +1,18 @@
+apiVersion: metrics.keptn.sh/v1
+kind: KeptnMetric
+metadata:
+  name: response-time
+spec:
+  fetchIntervalSeconds: 10
+  provider:
+    name: my-prometheus-provider
+  query: >-
+    "histogram_quantile(0.95, sum by(le) (rate(http_server_request_latency_seconds_bucket{job='{{.podtato-head-frontend-service}}'}[1m])))"
+---
+apiVersion: metrics.keptn.sh/v1
+kind: KeptnMetricsProvider
+metadata:
+  name: my-prometheus-provider
+spec:
+  type: prometheus
+  targetServer: "my-metrics-provider-url:9090"
diff --git a/docs/blog/posts/argocd-keptn-health/running-pods.png b/docs/blog/posts/argocd-keptn-health/running-pods.png
new file mode 100644
index 0000000000..55a48b5d3f
Binary files /dev/null and b/docs/blog/posts/argocd-keptn-health/running-pods.png differ