kyma
serving
kyma | serving | |
---|---|---|
5 | 7 | |
1,522 | 5,719 | |
0.3% | 0.6% | |
7.7 | 9.6 | |
26 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kyma
-
Giving Kyma a little spin ... a SpinKube
Although I had the project on my radar, I never took a closer look at it. However, now it was the time to give it a spin ... or try. All I needed was a Kubernetes environment. As I am working in the SAP space the choice of Kubernetes is kind of predefined, namely Kyma in its managed version on the SAP Business Technology Platform.
-
myNewsWrap: News from SAP and Microsoft - It's Season 2
News from the SAP side: the clear focus is here SAP Business Technology Platform especially Kyma
-
Production GraphQL repos in Go
I could only find https://github.com/kyma-project/kyma as something close to being real-world. But my google fu is failing here. Any help would be appreciated :)
-
Durable Functions with Netherite on Kyma
I am using Kyma as opinionated stack on top of Kubernetes (to be precise on a Gardener cluster) for this exercise. The setup should be similar for vanilla stacks, but the API gateway must be adjusted accordingly depending on what you use.
-
Road trip with my friends Kyma, KEDA and Azure Functions
So you can install Kyma 1.x without own domain, but you have no access to the Kyma console UI. An issue is open for this (https://github.com/kyma-project/kyma/issues/11924) and according to the Kyma slack channel the situation will improve with the upcoming release of Kyma 2.x, but until then you must provide an own domain to get access to the Kyma console UI. From my point of view this lifts the entry barrier of trying out open-source Kyma, but currently this is the way.
serving
-
We're Leaving Kubernetes
> You know that Cloud Run is a Kubernetes PaaS, right?
Yup. Isn't it Knative Serving or a home grown Google alternative to it? https://knative.dev/docs/serving/
The key is I am not managing Kubernetes and I am not paying for it - it is a fool's errand, and incredibly rarely needed. Who cares what is underneath the simple Cloud Run developer UX? What matters for me is cost, simplify and understandability. You get that with Cloud Run, and you don't with Kubernetes.
-
Building Microservices Using Knative
Knative Serving required
-
⚡⚡ Level Up Your Cloud Experience with These 7 Open Source Projects 🌩️
Knative
-
Running Serverless Functions on Kubernetes
~ kubectl apply -f \ https://github.com/knative/serving/releases/\ download/v$KNATIVE_VERSION/serving-crds.yaml ~ kubectl wait --for=condition=Established \ --all crd ~ kubectl apply -f \ https://github.com/knative/serving/releases/\ download/v$KNATIVE_VERSION/serving-core.yaml ~ kubectl wait pod --timeout=-1s \ --for=condition=Ready -l '!job-name' \ -n knative-serving > /dev/null
- Building functions with Knative and Tekton
- Kubernetes-based, scale-to-zero, request-driven compute
What are some alternatives?
vHive - vHive: Open-source framework for serverless experimentation
sdk-go - Go SDK for CloudEvents
spinkube-on-kyma - Installing SpinKube on Kyma
net-kourier - Purpose-built Knative Ingress implementation using just Envoy with no additional CRDs [Moved to: https://github.com/knative-sandbox/net-kourier]
spin-operator - Spin Operator is a Kubernetes operator that empowers platform engineers to deploy Spin applications as custom resources to their Kubernetes clusters