You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEPLOY.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,10 @@ For local development and testing, you can build and push the operator image dir
13
13
3. Add a version entry to `catalog/channels.yaml` following OLM upgrade specifications:
14
14
```yaml
15
15
entries:
16
-
- name: expiring-secret-operator.v0.0.1
17
-
- name: expiring-secret-operator.v0.0.2 # This is the next version to be released
16
+
- name: expiring-secrets.v0.0.1
17
+
- name: expiring-secrets.v0.0.2 # This is the next version to be released
18
18
skips:
19
-
- expiring-secret-operator.v0.0.1
19
+
- expiring-secrets.v0.0.1
20
20
```
21
21
4. Render, build, and push the catalog index:
22
22
```sh
@@ -33,10 +33,10 @@ A catalog release is triggered if:
33
33
- A new version entry is specified in `catalog/channels.yaml,` indicating the upcoming release.
34
34
```yaml
35
35
entries:
36
-
- name: expiring-secret-operator.v0.0.1
37
-
- name: expiring-secret-operator.v0.0.2 # This is the next version to be released
36
+
- name: expiring-secrets.v0.0.1
37
+
- name: expiring-secrets.v0.0.2 # This is the next version to be released
38
38
skips:
39
-
- expiring-secret-operator.v0.0.1
39
+
- expiring-secrets.v0.0.1
40
40
```
41
41
42
42
## Working with Entries in `catalog/channels.yaml`
@@ -61,29 +61,29 @@ Example:
61
61
62
62
```yaml
63
63
entries:
64
-
- name: expiring-secret-operator.v0.0.3
64
+
- name: expiring-secrets.v0.0.3
65
65
skips:
66
-
- expiring-secret-operator.v0.0.1
67
-
- expiring-secret-operator.v0.0.2
66
+
- expiring-secrets.v0.0.1
67
+
- expiring-secrets.v0.0.2
68
68
```
69
69
#### Breaking API Changes (Use replaces)
70
70
For breaking API changes, the replaces field is used to specify which previous version is being replaced. This indicates to OLM that the older version should be upgraded to the new version.
71
71
Example:
72
72
73
73
```yaml
74
74
entries:
75
-
- name: expiring-secret-operator.v0.0.3
76
-
replaces: expiring-secret-operator.v0.0.1
75
+
- name: expiring-secrets.v0.0.3
76
+
replaces: expiring-secrets.v0.0.1
77
77
```
78
78
79
79
## Contributing
80
80
1. Add the next version entry in `catalog/channels.yaml`:
81
81
```yaml
82
82
entries:
83
-
- name: expiring-secret-operator.v{{CURRENT}}
84
-
- name: expiring-secret-operator.v{{NEXT}}
83
+
- name: expiring-secrets.v{{CURRENT}}
84
+
- name: expiring-secrets.v{{NEXT}}
85
85
skips:
86
-
- expiring-secret-operator.v0.0.1
86
+
- expiring-secrets.v0.0.1
87
87
```
88
88
2. Create a PR and run tests.
89
89
3. Merging the PR will trigger the build and push the releases.
0 commit comments