As a user I would like Ability to deploy workloads outside of the local kubernetes cluster to use cloud native runtime for my services.

[scheuk]

Our use case is to use KLT to deploy services/containers into cloud native runtimes like GCP cloud run or AWS lambda or other infrastructure items that live outside of k8s including database migrations, infrastructure configuration (IAC/terraform), etc.
This is currently theoretically possible with KeptnV1 as the Job Executor Service can execute anything for the deployment.
Also with KeptnV1 we can define an arbitrary sequence of events for a service deployment which could include running terraform, database migrations, deployments, tests, etc.

[thisthat]

Hey @scheuk, thanks for the suggestion. In our backlog, we have #614 to provide the capabilities of the Job Executor Service directly in KLT.
For your second point, we want to support users only when manifests hit the Kubernetes cluster, i.e., we can help you with db migration before the deployments, deployments, tests etc.

I can recommend the use of Tekton or Argo to orchestrate workflows that do some work, i.e., terraform, before your manifests hit your cluster.

[scheuk]

Yeah that makes sense.
I see that the workflow/shipyard component is gone with KLT and a generic workflow engine would work.
However it would be nice to use the SLI/SLO checking and test execution workflows in KLT against service deployments that are external to the cluster. Ie serverless/cloudrun deployments.

[agardnerIT]

Keptn V1 is still available

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.

[thisthat]

Hey @scheuk :)
With the Container Runtime support, you can now do the same things you could do with JES: https://lifecycle.keptn.sh/docs/migrate/strategy/#integrations-and-services-in-jes

I am closing the issue but feel free to re-open it if you have further feedback/questions :)