kcp
kubevela
kcp | kubevela | |
---|---|---|
8 | 28 | |
2,246 | 6,123 | |
1.0% | 2.0% | |
9.2 | 8.7 | |
7 days ago | 10 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.
kcp
-
Kubernetes as a Platform vs. Kubernetes as an API
I think that's the actual goal of kcp: https://github.com/kcp-dev/kcp
- Can someone explain this please?
-
kcp is a prototype of a multi-tenant Kubernetes control plane for workloads on many clusters
The Goals.md was a far better introduction, but still a bit abstract. Needs pictures!
-
Tools to Run Kubernetes Locally
I agree with this. Also, have you seen the kcp project? Seems like a promising experiment.
https://github.com/kcp-dev/kcp
-
NSA Kubernetes Hardening Guidance [pdf]
And making it so that "many clusters" look exactly like "one cluster" is one of the goals the kcp prototype was exploring (although still early) because I hear this ALL the time:
1. 1 cluster was awesome
2. Many clusters means I rebuild the world
3. I wish there was a way to get the benefits of one cluster across multiples.
Which I believe is a solvable problem and partially what we've been poking at at https://github.com/kcp-dev/kcp (although it's still so early that I don't want to get hopes up).
-
Ask HN: What do you think will come after Kubernetes?
Simpler and monolith has it's place, but I see it as impossible for any "simple" solution to ever gain enough mindshare to win. A lot of people suggesting monoliths & hosted services, but they are never going to have the community, the presence of something like Kubernetes, which unites people, which people collaborate over, in the same way we all got to learn & experience & co-develop for Docker. The question posted somewhat gets it wrong, "Kubernetes became a thing after Docker became a thing (and so on," implies that they're different things, that tech is about different things, but in many ways Kubernetes is a natural extension & outgrowth, it is a part of the Docker scene, & has continuity with it.
Kubernetes is a thing now, but it's patterns are still underspoken of, underpracticed, underdeployed to the rest of the software world. We will get better at being like Kubernetes, for great benefit. Folks learning how control-loops are advantageous, and learning to use universal API Servers for all their systems will continue to drive not just Kubernetes, but the patterns underlying Kubernetes further into our applications & services & technologies. Tech like KCP[1] is an early indicator of this interest, in using the soul of kubernetes if not it's specific machinery, by creating an independent, non-Kubernetes, but Kubernetes compatible API Server. Having universal storage, having autonomic system control are huge advantages when system building, and gaining those benefits is fairly easy, with or without Kubernetes itself.
I'm hoping we see a DIY cloud'ing become more of a thing. Leaving everything in the hands of hyperscalers is a puzzling and hard to imagine state of affairs, given the hardware nirvana we've experienced in the past two plus decades. Kubernetes is the first viable multi-system operational paradigm, the first diy-able cloud we have, and it's shocking it took that long, but smaller practitioners getting good at converting their sea of individual boxes into something more resembling the Single System Image dreams of old, albeit through a highly indirect Kubernetes-ish route, is a decade or decades long quest we seemingly just started in to a couple years ago.
I'm hoping eventually ubiquotous and pervasive computing starts to dovetail with this world, that we start to have better view & visibility of all the computing resources around us, via standardized, well known interfaces. Rather than the hodgepodge of manufacturer controlled, invisible, un-debuggable overlay networks that alas, constitute the vast majority of the use of the internet these days. Alas the news there is never good, the new Matter standard is, like Thread, inaccessible, unviewable; consumers are expected to remain dumb, ignorant, unaware of how any of it works, merely thankful for whatever magic they receive[2][3]. But as a home-cloud, as the manor re-establishes computing as base & competency for itself (#ManorCompute), & as good projects like WebThings[4] or whatever takes it's place light the darkened damp corridors only robots patrolled, I hope for a reawakening, hope a silent majority becomes more real & known, hope the fed up, sick of this shit, disgusted with remote-service-based technology world starts to manifest & apply real pressure to emerge a healthy, pro-human, pro-user ubiquotous & pervasive computing that gives us an honest shake, that shows what it is, that integrates into our personal home clouds.
I think there's a huge pent up demand & desire for flow-based/evented systems, for Yahoo Pipes, for Node-RED[5]. The paradigm needs help, I think there's too many missing pieces for something like Node-RED to be the one, but re-emerging user-control, giving us ALL flexible means to compute, is key. Exposing & embracing some level of technical literacy is something people want, but no one knows how to articulate it or what they want. We're mired in a "faster horses" stage, and it's fundamentally incorrect.
Last, I have huge hopes for the web. There are incredibly awesome advances being made in the range of peripherals, devices, capabilities the web supports. The web can do so much more. We're barely beginning to use the cutting edge ServiceWorkers, barely beginning to use Custom Elements ("WebComponenets"), and these aren't even that new any more. These are fundamentally revolutionary technologies. Things like File System Access just came back on the scene after over a decade of going nowhere. Secondary screen working group is tying together multiple systems in interesting ways. There's a lot of high-tower shit, in WebAssembly (especially when Interface Bindings starts to allow real interop with JS), in TypeScript, but to me, I think rather than just building up up up there's some very real re-assessments we ought to be making about how and what we build. Trying to make self-documenting machines, trying to make computing visible, these aren't concerns of industrial computing, but they are socially invaluable advances that have been somewhat on hold in the age of Pax React-us, and we're well over half a decade in & while there's endless areas to learn about, improve, get better at in this highly industrialized toolset, I want to think there are some slumbering appetites, some desires to re-assess. I'm a bit afraid/scared of WebAssembly being a huge tower-of-babel time-sink/re-industrializing-focus that distracts from the need for a new vision quest, but I have hope too, I see the yearning. Albeit often expressed in lo-fi counter-culture, which to me is a distraction & avoidance, rather than the socially empowering act that has been a quiet part of the web's promise[6].
[1] https://github.com/kcp-dev/kcp
[2] https://staceyoniot.com/project-chip-becomes-matter/
[3] https://news.ycombinator.com/item?id=27123944
[4] https://webthings.io/
[5] https://nodered.org/
[6] https://webdevlaw.uk/2021/01/30/why-generation-x-will-save-t...
- KCP: A Minimal Kubernetes API Server
kubevela
- Open-source alternative to Heroku, Vercel, and Netlify
- Is there any Django app deployment tool for VPS-based environments with UI?
- What's the status of Open Application Model?
-
Using compose files as a universal infrastructure interface, even for Kubernetes
Finally, I think the OAM model offers one possible future. Take a look at projects like KubeVela and Crossplane. These allow you to compose your own custom abstraction layer. The developer creates a simple CRD called "Application" and this is translated into ths k8s or even off-cluster resources. Problem right now is the complexity is transferred onto guys configuring the platform..... I want to see more "out of the box" implementations.
- Helm or Kustomize for my situation?
- KubeVela, the extensible engine for IDP and platform engineering
-
Opinionated application platform on top of Kubernetes?
Gotcha, thanks! We already run ArgoCD but having devs write raw manifests feels so low-level when it’s usually the same combo of configmaps, ingresses, services, deployments… Maybe this is more in the direction of what I’m looking for? 🤔 https://kubevela.io
-
Finding better motivations for software work (Other than pride)
Note: On that topic, I'm keeping a close eye on the Open Application Model and the kubevela projects. I think it’ll help write a representation of an application and its components that we can validate the structure of our code against, and generate documentation from it. Not a complete solution to the problem, but it'll help with certain parts of architecture documentation
- Kubevela - The modern application platform.
-
Clusterpedia —— Cluster API Searching Has Never Been Easier
Also, kubevela is getting ready to connect to clusterpedia https://github.com/kubevela/kubevela/issues/4237,
What are some alternatives?
karmada - Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration
crossplane - The Cloud Native Control Plane
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
argo-cd - Declarative Continuous Deployment for Kubernetes
kpt - Automate Kubernetes Configuration Editing
kustomize - Customization of kubernetes YAML configurations
cnab-spec - Cloud Native Application Bundle Specification
rancher - Complete container management platform
tutorialinux-hashistack - A hands-on learning project for consul, using Terraform
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
awesome-k8s-security - A curated list for Awesome Kubernetes Security resources
porter - Kubernetes powered PaaS that runs in your own cloud.