ContainerApplicationGenericLabels
ContainerApplicationGenericLabels copied to clipboard
Default Containerized Application Labels used to document the application and/or image
Please drop the `authoritative-source-url` label from the specification: - It is easy for this to become stale over time as organizations rename their public-facing registries. - This label cannot support...
The document states that these two labels are required: * io.k8s.display-name (Name of the container displayed in Kubernetes) * io.openshift.tags (tags used by searching engine, e.g. "builder,php,php56,rh-php56") Is that true?...
Related: https://github.com/user-cont/colin/issues/165
The `help` label is used by atomic, but is not documented in this repository. IMO it also caused the issue tracked in https://pagure.io/atomic-wg/issue/267, which was also reported to https://github.com/projectatomic/atomic/issues/967. Once...
The "usage" label has recently turned up in rhel75 images: "usage": "This image is very generic and does not serve a single use case. Use it as a base to...
Describing environment variables shouldn't be exclusive to the nulecule spec https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/master/vendor/projectatomic/labels.md
The description is confusing. As the labels listed in other labels are also mandatory.
There are some nice existing OpenShift labels which are missing: https://docs.openshift.com/enterprise/3.0/creating_images/metadata.html
I've totally missed the /vendor folder. Links should be included in the main readme.
I would like to propose a `License` label that contains license information about the image. It will carry string containing license information. Could be simply the name of the license...