-
Notifications
You must be signed in to change notification settings - Fork 0
CNCF application
Comma-separate multiple emails here
Provide the email address(es) of individuals who should be contacted regarding this application. If more than one email is provided, please comma separate them.
One-line summary of the project Provide a very brief, single line summary of the project.
Kubero provides a simple way to deploy 12-factor apps to kubernetes by using GitOps or containers.
Describe what it does and why it's needed. Provide a brief, 100-300 word description of the project that explains what it does and why it's needed.
Deploying applications on Kubernetes can be complex and requires a solid understanding of Kubernetes
concepts, as well as proficiency in writing Helm or Kustomize manifests. **Kubero** simplifies
this process by providing developers with an intuitive, user-friendly interface—either through a
GUI or CLI—that streamlines deployment using standardized procedures aligned with the 12-factor app
principles. By automating adherence to best practices, Kubero enhances security while minimizing the
operational burden. Its primary goal is to reduce the barriers for developers, making it easier to deploy,
publish, and maintain applications on Kubernetes with minimal friction.
Add org URL here Provide the URL of GitHub or Gitlab organization of the projects if all repos under the org are in scope of the application. If no organization, provide "N/A".
https://github.com/kubero-dev
Add code repo URL here Provide the URL of the primary source code for the project. If there is no single repo but all repos under the org are in scope of the application, provide "N/A". If multiple repos (in addition to the primary repo) exist under an org, but not all are in scope, please enumerate in scope repos in the next question.
https://github.com/kubero-dev/kubero
Add additional repo URLs here Provide the URLs of any additional repos for this project's application if appropriate.
https://github.com/kubero-dev/kubero-operator
https://github.com/kubero-dev/kubero-cli
https://github.com/kubero-dev/docs
Add website URL here Provide the URL of the project's website. If the project has no website, please provide the primary repo URL again.
https://www.kubero.dev
Add Roadmap URL here Provide the URL of the project's roadmap.
https://github.com/orgs/kubero-dev/projects/1
You may optionally provide any details of the roadmap you feel are required for clarity.
Add Contributing guide URL here Provide the URL of the project's contribution guide. If the guide is embedded in another file, please deep link to the correct header.
https://github.com/kubero-dev/kubero/blob/main/CONTRIBUTING.md
Add CoC URL here Provide the URL of the project's code of conduct.
https://github.com/kubero-dev/kubero/blob/main/CODE_OF_CONDUCT.md
Add Adopters URL here Provide the URL of the project's Adopters file. If no file exists, move on to the next question.
Add sponsoring company or org URL here Provide the URL of the project's contributing or sponsoring company/organization. If no such company/organization exists move on to the next question.
N/A
Add maintainer URL here Provide the URL of the project's maintainers file.
https://github.com/kubero-dev/kubero/blob/main/MAINTAINERS.md
By submitting this issue, you understand that if accepted, the project will be required to follow the CNCF IP Policy located at https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
yes
Trademark and accounts By submitting this issue, you understand that if accepted, all project trademarks (such as the project name) and accounts will be donated to the CNCF. For more information please refer to the CNCF IP Policy.
yes
yes
The CNCF can provide the project with... Why do you want to contribute the project to the CNCF? What value does being part of the CNCF provide the project? Provide detail on why you chose the CNCF that allows the TOC to consider alignment of expectations between the project and the ecosystem.
Contributing Kubero to the CNCF offers several key benefits for both the project and the
broader cloud-native community. As a project maintained by a single developer, joining
CNCF would provide a collaborative ecosystem where Kubero can gain visibility, credibility,
and access to a larger pool of contributors. This ensures long-term sustainability by
distributing maintenance efforts and promoting open governance.
CNCF offers a well-established platform that fosters innovation and ensures that cloud-native
projects grow with community support. By contributing Kubero to CNCF, the project would align
with CNCF's mission of democratizing cloud-native technologies, accelerating its evolution and
adoption in line with industry best practices.
By becoming a CNCF project, Kubero would be validated through the CNCF’s robust governance
model, encouraging broader adoption and increasing confidence among users and contributors.
This project benefits the landscape by... How will adding this project benefit the CNCF landscape? What is the differentiator or enhancement this project provides to existing project, capabilities, or challenges within the landscape?
Kubero can bring several benefits to the CNCF landscape by enhancing the ecosystem with a
user-friendly tool focused on simplifying Kubernetes deployments. While many CNCF projects
focus on various aspects of cloud-native infrastructure, Kubero's strength lies in
streamlining the deployment process, making it accessible for both small teams and large enterprises.
A key differentiator is its focus on automation and ease of use, reducing the need for
deep Kubernetes expertise to efficiently manage applications. Kubero integrates well with
existing CNCF projects, such as Helm and ArgoCD, but stands out by providing an intuitive
interface and automation for deployment workflows, making Kubernetes adoption easier for
non-expert users.
By addressing the challenge of Kubernetes complexity, Kubero fills a gap in the CNCF landscape,
complementing other projects by lowering the barrier for entry, encouraging broader adoption
of Kubernetes, and contributing to the overall goal of simplifying cloud-native technologies.
This project... Please explain where you see the project "fitting" in the Cloud Native landscape. This should detail how the project is cloud native, which elements of cloud native the project embodies or exemplifies.
Kubero fits well within the Cloud Native landscape as it exemplifies key principles
like scalability, automation, and container orchestration, which are core to cloud-native
applications. As a Kubernetes deployment tool, Kubero is inherently cloud-native because
it operates within the Kubernetes ecosystem, leveraging its strengths in container
orchestration and management.
The project embodies cloud-native elements by promoting:
- Self-service and rapid provisioning: Kubero abstracts infrastructure management
and simplifies setup, making it quick for developers to get applications running in
the cloud without specialized Kubernetes knowledge
- Scalability: It allows for easy scaling of applications based on demand, leveraging
Kubernetes’ native capabilities for scaling pods and services.
- Automation: Kubero enhances automation by simplifying the deployment pipeline,
making CI/CD workflows more accessible, and ensuring that application updates and
rollouts can happen seamlessly and automatically.
- Portability: By building on Kubernetes, it ensures that applications are portable
across cloud providers and on-prem environments, consistent with the cloud-native
emphasis on flexibility and avoiding vendor lock-in.
- Resilience: Through automated deployments and rollbacks, Kubero supports self-healing,
a key aspect of cloud-native applications.
By integrating these principles, Kubero strengthens cloud-native application development
and management, promoting Kubernetes adoption across the CNCF ecosystem.
What CNCF projects does this project complement or depend on, and how?
- Kubernetes
- buildpacks.io
- Operator Framework
- Prometheus
- Cert Manager
What CNCF projects does this project overlap with, and how?
Kubero overlaps with several CNCF projects, particularly in the Kubernetes ecosystem,
but it complements them with a unique focus on simplifying application deployment
workflows. Here are key overlaps:
- ArgoCD: Both Kubero and ArgoCD focus on automating deployments. However, while ArgoCD
focuses on GitOps for continuous delivery, Kubero integrates Git-based deployments with
a more Heroku-like developer experience. It pulls code, runs build scripts, and deploys
applications without requiring Docker images, which contrasts with Argo CD's
container-centric approach
- Flux: Flux focuses on continuous and declarative Kubernetes application management
using GitOps principles, which overlaps with Kubero's automated deployments triggered
by Git. However, Kubero integrates more tightly with the build and execution phases,
allowing developers to deploy code changes instantly without Dockerfile or manifest
creation
- Tekton: Like Tekton, Kubero includes a CI/CD pipeline. However, Kubero's pipeline
is optimized for speed and simplicity, as it bypasses the traditional container
build-push-pull workflow. Instead, it directly runs build scripts from the code
repository, making it faster than Tekton, which often involves container builds and
more complex workflows
Kubero stands out by providing simplicity, reducing the complexity of using these tools
individually or together. It complements these projects by addressing the need for a
more intuitive deployment process, especially for smaller teams or less experienced
Kubernetes users.
By leveraging these differences, Kubero targets developers seeking rapid, Heroku-like
simplicity for Kubernetes application deployments.
Please list similar projects in the CNCF or elsewhere. If none exist, provide "N/A".
- Coolify
- Caprover
Are you already listed on the CNCF Landscape?
Yes. Kubero is listed under "Certified providers and partners/Paas and Container Services"
and should be moved to "Projects and Products/Continuous Integration & Delivery"
https://landscape.cncf.io/?item=platform--paas-container-service--kubero
If this project is identical (name, features, etc.) or closely related to one or more products or services of the sponsoring company/organization(s), how do you plan to separate this project from any products in terms of organization and development? If it is not related to a product or service, just provide "N/A".
N/A
Has your project been presented to any TAG? If so, please link meeting notes and/or recordings as applicable.
No
Please list any people who are part of CNCF leadership (TOC, TAGS, etc.) who can endorse or answer questions about your project.
N/A
Any additional information you would like the TOC to consider when evaluating this project?
N/A