You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
The example in the README shows deploying a runtime.yaml file for Python37, but that file doesn't exist for Python310. How would I go about installing/deploying a Python310 Lambda function with KLR?
The text was updated successfully, but these errors were encountered:
Hi, @beck3905. Our old runtimes (python37, ruby25, node10, etc.) were built as a part of our serverless initiative and were meant to be used with the tm CLI and tekton build pipelines. Since the time the KLR project was first introduced, we've shifted our focus toward event-driven architecture where KLR is represented as our Function custom resource. Compared to the original KLR, Functions are supposed to be easier to use, although, a bit less flexible (no external dependencies). The latest Python KLR is available in the Triggermesh starting the version v1.24.2. I don't think that we'll be updating tekton-based KLR manifests, but if you up to contributing to the project we'll support you and help with the PR.
You're welcome to join our Slack where we can discuss any related topics: https://join.slack.com/t/triggermesh-community/shared_invite/zt-1kngevosm-MY7kqn9h6bT08hWh8PeltA
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The example in the README shows deploying a runtime.yaml file for Python37, but that file doesn't exist for Python310. How would I go about installing/deploying a Python310 Lambda function with KLR?
The text was updated successfully, but these errors were encountered: