Cloud Native Application Bundles (CNAB) are a package format specification that describes a technology for bundling, installing, and managing distributed applications, that are by design, cloud agnostic.
CNAB Core 1.0 (Final)
The CNAB Working Group with the joint approval of the Executive Directors has approved the CNAB Core 1.0 specification for publication. CNAB Core 1.0 is complete.
For more information on the approval process, see the process documentation. Further changes to CNAB Core will be considered for CNAB Core 1.1.
We operate a mailing list via the Joint Development Foundation.
Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119.
The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the rationale for the C99 standard.
An implementation IS compliant if it satisfies all the MUST, REQUIRED, and SHALL requirements.
An implementation IS NOT compliant if it fails to satisfy one or more of the MUST, REQUIRED, or SHALL requirements.
Document Naming Conventions
The CNAB Core specification is contained in the 1xx documents.
The CNAB Registry specification is contained in the 2xx documents.
The CNAB Security specification reserves 3xx level documents.
The Claims specification reserves 4xx documents.
The CNAB Dependencies specification uses 5xx documents.
The 8xx-level documents are reserved for non-normative guidance.
The 9xx-level documents are reserved for process documents.
Cloud Native Application Bundle Specifications
Abstract
Cloud Native Application Bundles (CNAB) are a package format specification that describes a technology for bundling, installing, and managing distributed applications, that are by design, cloud agnostic.
CNAB Core 1.0 (Final)
The CNAB Working Group with the joint approval of the Executive Directors has approved the CNAB Core 1.0 specification for publication. CNAB Core 1.0 is complete.
For more information on the approval process, see the process documentation. Further changes to CNAB Core will be considered for CNAB Core 1.1.
Table of Contents
Contributing
The specification is licensed under OWF Contributor License Agreement 1.0 - Copyright and Patent in the LICENSE file.
Communications
Meetings
Slack Channel
cnab Slack channel for related discussion in
CNCF's Slack workspace.
Mailing List
We operate a mailing list via the Joint Development Foundation.
Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119.
The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the rationale for the C99 standard.
An implementation IS compliant if it satisfies all the MUST, REQUIRED, and SHALL requirements.
An implementation IS NOT compliant if it fails to satisfy one or more of the MUST, REQUIRED, or SHALL requirements.
Document Naming Conventions
GITHUB