This repository contains a curated set of image streams and templates for OpenShift 3. See the official OpenShift documentation for more information about image streams and templates.
Provided and supported by Red Hat, official Templates and ImageStreams are listed in the top level of this repository, making it easy for developers to get started creating applications with the newest technologies.
You can check to see which of the official Templates and ImageStreams are available in your OpenShift cluster by doing one of the following:
-
Log into the web console and click Add to Project
-
List them for the openshift project using the Command Line Interface
$ oc get templates -n openshift
$ oc get imagestreams -n openshift
Community templates and image streams are not provided or supported by Red Hat. This curated list of community maintained resources exemplify OpenShift best practices and provide clear documentation to serve as a reference for other developers.
$ pip install -r requirements.txt
$ make import
$ make verify
The make verify command runs the following checks:
- verifies YAML syntax
- verifies the Python script (using pylint)
- verifies that make import has been run
- Fork the openshift/library repository on github
- Add your template or image stream to the community.yaml file in the top level of this project
- Run the
make importcommand and make sure that your template(s) and/or image-stream(s) are processed and written to the correct directory under the community folder and that no errors have occurred. - Run the
make verifycommand and ensure that no errors occur - Commit and push your changes to your fork of the github repository
- Make sure to commit any changes in the community folder
- Create a pull request against the openshift/library upstream repository
That's it! Your pull request will be reviewed by a member of the OpenShift Team and merged if everything looks good.
variables: # (optional) top level block item
<variable_name>: <value> # (optional)
data: # (required) top level block item
<folder_name>: # (required) folder that the below items will be stored in
imagestreams: # (optional) list of image-streams to process into the above folder
- location: # (required) github url to a json file or folder of json files
regex: # (optional) matched against ['metadata']['name'] in the json file
suffix: # (optional) suffix for the file that is created ex: ruby-<suffix>.json
docs: # (optional) web address of the documentation for this image-stream
templates: # (optional) list of templates to process into the above folder
- location: # (required) github url to a template or folder of templates in json format
regex: # (optional) matched against ['metadata']['name'] in the json file
suffix: # (optional) suffix for the file that is created ex: ruby-<suffix>.json
docs: # (optional) web address of the documentation for this template
Anything under the data block can contain a reference to a variable by using the following syntax:
{variable_name}
You must also specify a value for that variable name under the variables block with the following syntax:
<variable_name>: <value>
Listings in the official.yaml file will be created in a sub folder of the official top level folder. Listings in the community.yaml file will be created in a sub folder of the community top level folder.
The folder_name is a sub folder which represents a logical grouping for a set of templates or image-streams in the top level official or community folders.
The location must be a publicly available url that points to either a template, image-stream, or image-stream list file in JSON or YAML format
The docs is a field to list the web address of the documentation for the template, image-stream, or image-stream list
The regex is a plain string that is matched against the ['metadata']['name'] element in the template or image-stream. Make sure that the regex string that you provide is descriptive enough to only match the ['metadata']['name'] that you are trying to target.
The suffix is applied to the end of the filename that is created right before the .json file extension and can contain dashes (-) or underscores (_).
You can find more information about creating templates and image-streams in the official OpenShift Documentation. Below are some quick links to important sections: