[Sandbox] Shipwright - Githubissues

qu1queee commented 5 months ago

Application contact emails

encalada@de.ibm.com schwarzs@de.ibm.com adam.kaplan@redhat.com

Project Summary

An extensible framework for building container images on Kubernetes.

Project Description

Shipwright is designed to make it easy to build container images securely and reliably. The community is rooted in the fundamental principles of simplicity, flexibility, and security. Shipwright is currently an incubating project under the Continuous Delivery Foundation (a subsidiary of the Linux Foundation).

This project introduces a layer of standardisation across many of today's build tools (such as Kaniko, ko or Buildpacks). By abstracting the complexity of today's build processes, Shipwright establishes a common layer within Kubernetes, that can work across multiple tools and runtimes.

In essence, Shipwright empowers developers and organisations to easily build container images, leveraging their preferred build tools with the confidence of adhering to security best practices. Shipwright extensible and pluggable nature, makes it an invaluable asset for integration into existing Kubernetes components or CI/CD systems.

Org repo URL (provide if all repos under the org are in scope of the application)

https://github.com/shipwright-io

Project repo URL in scope of application

N/A

Additional repos in scope of the application

N/A

Website URL

https://shipwright.io

Roadmap

https://github.com/shipwright-io/build/blob/main/ROADMAP.md

Roadmap context

No response

Contributing or Sponsoring Org

https://www.ibm.com/, https://www.redhat.com/ . Contributors are primarily employees from IBM and RedHat. Project Shipwright is already a vendor-neutral Linux Foundation Project, incubating inside the Continuous Delivery Foundation.

Maintainers file

https://github.com/shipwright-io/build/blob/main/OWNERS

IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?

Shipwright is currently an incubating project within the Continuous Delivery Foundation (CDF). After further evaluation, we believe the project is more closely aligned with the CNCF. We are confident the CNCF will help us increase community contributions and adoption, and foster closer collaboration with our mutual project dependencies.

The goals of our project align with the CNCF Sandbox goals and with CNCF's mission by addressing key challenges in the Cloud Native space related to application delivery. Shipwright empowers organisations to build and run scalable applications in today's diverse cloud environments.

Benefit to the Landscape

In the evolving landscape of today's Cloud Native ecosystem, developers encounter a multitude of build tools for creating container images. Project Shipwright addresses this variety by introducing standardisation across multiple CNCF build tools, promoting their adoption through an extensible declarative API accessible to both developers and organisations.

This standardisation can be consumed by other projects that aim to provide a unique experience when building and deploying applications, using Shipwright as a fundamental building block.

In addition, Project Shipwright aims to provide throughout the same declarative API, today's Supply Chain Security Best Practices.

Cloud Native 'Fit'

Shipwright is build with and for Cloud Native technologies, fitting into the Application Definition & Image Build category.

Cloud Native 'Integration'

We complement the following projects:

OpenFunction
- How?
  - Uses Shipwright as a Building Block
Tekton
- How?
  - Can integrate Shipwright inside a Tekton Pipeline, as the building block.

We depend on the following projects:

ko
- How?
  - Shipwright can use ko to delegate the mechanism of building a container image.
Buildpacks
- How?
  - Shipwright can use Buildpacks to delegate the mechanism of building a container image.
Kaniko
- How?
  - Shipwright can use Kaniko to delegate the mechanism of building a container image.
Tekton
- How?
  - Shipwright uses Tekton to achieve the sequential execution of containers inside a Kubernetes Pod, plus other Tekton features.

Cloud Native Overlap

None.

Similar projects

N/A

Landscape

Yes.

Business Product or Service to Project separation

N/A

Project presentations

N/A

Project champions

Karena Angell
Derek Carr

Additional information

Our decision to contribute the project to CDF was primarily driven by its integration with Tekton, Shipwright is built on Tekton, a CDF project since its inception. However, we anticipate that this association will become less influential over time, especially in light of Tekton's departure from CDF and the growing number of CNCF projects used by or that rely on Shipwright.

angellk commented 5 months ago

@qu1queee are you available April 3 to present to TAG App Delivery?

qu1queee commented 5 months ago

@angellk yes, I'm available.

pgonin commented 4 months ago

Interestingly, Kaniko is also candidate https://github.com/cncf/sandbox/issues/88

angellk commented 4 months ago

@qu1queee we'd like to move your presentation from 4/3 to 3/6 (this coming wednesday) - are you available?

qu1queee commented 4 months ago

We will give an introduction on the Project to the TAG App delivery on 3rd of April. Just for the record.

TheFoxAtWork commented 3 days ago

@lianmakesthings - Does TAG App Delivery have a recommendation on this project?

cncf / sandbox

[Sandbox] Shipwright #85