@@ -13,17 +13,21 @@ The first PR targets this repository and:
13
13
14
14
- bumps the [ ` VERSION ` ] ( VERSION ) file to the target version
15
15
- changes the ` images ` ` newName ` /` newTag ` fields of
16
- [ ./deploy/base /kustomization.yaml] ( deploy/base /kustomization.yaml ) from
17
- ` gcr.io/k8s-staging-sp-operator/security-profiles-operator ` to
16
+ [ ./deploy/kustomize-deployment /kustomization.yaml] ( deploy/kustomize-deployment /kustomization.yaml )
17
+ from ` gcr.io/k8s-staging-sp-operator/security-profiles-operator ` to
18
18
` k8s.gcr.io/security-profiles-operator/security-profiles-operator ` (` newName ` ) and the
19
19
corresponding tag (` newTag ` ). After that the make target ` make bundle `
20
20
has to be run and the changes have to be committed.
21
- - changes the tag in the same way in the OLM example manifest at
21
+ - changes the ` image ` in the ` CatalogSource ` in the same way at
22
22
[ ./examples/olm/install-resources.yaml] ( /examples/olm/install-resources.yaml )
23
23
- changes [ ` hack/ci/e2e-olm.sh ` ] ( /hack/ci/e2e-olm.sh ) to sed
24
- ` "s#k8s.gcr.io/security-profiles-operator/security-profiles-operator-catalog:v0.4.3 #${CATALOG_IMG}#g" `
24
+ ` "s#k8s.gcr.io/security-profiles-operator/security-profiles-operator-catalog:v0.0.0 #${CATALOG_IMG}#g" `
25
25
instead of
26
26
` "s#gcr.io/k8s-staging-sp-operator/security-profiles-operator-catalog:latest#${CATALOG_IMG}#g" `
27
+ (please note to change the version ` v0.0.0 ` to the upcoming release)
28
+ - updates [ ./dependencies.yaml] ( ./dependencies.yaml ) ` spo-current ` version as
29
+ well as its linked files. Run ` make verify-dependencies ` to verify the
30
+ results.
27
31
28
32
After this PR has been merged, we have to watch out the successful build of the
29
33
container image via the automatically triggered
@@ -64,9 +68,9 @@ After that, another PR against this repository has to be created, which:
64
68
- bumps the [ ` VERSION ` ] ( VERSION ) file to the next minor version, but now including the
65
69
suffix ` -dev ` , for example ` 1.0.0-dev ` .
66
70
- changes the ` images ` ` newName ` /` newTag ` fields in
67
- [ ./deploy/base /kustomization.yaml] ( deploy/base /kustomization.yaml ) back to
68
- ` gcr.io/k8s-staging-sp-operator/security-profiles-operator ` ( ` newName ` ) and ` latest `
69
- (` newTag ` ) and runc ` make bundle `
71
+ [ ./deploy/kustomize-deployment /kustomization.yaml] ( deploy/kustomize-deployment /kustomization.yaml )
72
+ back to ` gcr.io/k8s-staging-sp-operator/security-profiles-operator `
73
+ (` newName ` ) and ` latest ` ( ` newTag ` ) and runc ` make bundle `
70
74
- changes the tag in the same way in the OLM example manifest at
71
75
[ ./examples/olm/install-resources.yaml] ( /examples/olm/install-resources.yaml )
72
76
- reverts the changes to [ ` hack/ci/e2e-olm.sh ` ] ( /hack/ci/e2e-olm.sh )
0 commit comments