-
Notifications
You must be signed in to change notification settings - Fork 3
/
operator-index.yml
41 lines (39 loc) · 1.45 KB
/
operator-index.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
---
# These are the bundles that are listed in the catalog index
operator_bundles:
- name: sonarqube-operator
img: quay.io/redhatgov/sonarqube-operator-bundle
tag: 0.0.5
- name: gitea-operator
img: quay.io/redhatgov/gitea-operator-bundle
tag: 0.0.7
- name: nexus-operator
img: quay.io/redhatgov/nexus-operator-bundle
tag: 0.0.11
- name: mattermost-operator
img: quay.io/redhatgov/mattermost-operator-bundle
tag: 1.0.0
- name: selenium-grid-operator
img: quay.io/redhatgov/selenium-grid-operator-bundle
tag: 0.0.2
- name: ploigos-operator
img: quay.io/redhatgov/ploigos-operator-bundle
tag: 0.22.1
- name: devsecops-operator
img: quay.io/redhatgov/devsecops-operator-bundle
tag: 0.0.4
# - name: your-operator
# bundle_img: quay.io/your-project/your-operator-bundle
# bundle_tag: latest
# This is information on the catalog index image that will be built
catalog_index:
img: quay.io/redhatgov/operator-catalog
tag: 2.0.7
# If we remove a bundle from the index, we should increase the major version, as
# this is a breaking change.
# If we add a bundle to the index, we should increase the minor version, as this
# is a backwards-compatible change.
# If we update a bundle's tracking tag, or perform some other small bugfix, we
# should increase the patch version, as this is likely a minor bugfix/
# enhancement. If an operator has a pinned version change that breaks its own
# API (for example, moving from major version `1` to `2`),