-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STF 1.5.5 release ops #161
Changes from all commits
5687756
9d8bbb6
dde1677
432d7cb
c11cfee
32ef756
bcdd74d
dd9da06
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,7 +13,7 @@ LABEL operators.operatorframework.io.metrics.mediatype.v1=metrics+v1 | |
LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v0.19.4 | ||
LABEL operators.operatorframework.io.metrics.project_layout=ansible | ||
LABEL com.redhat.delivery.operator.bundle=true | ||
LABEL com.redhat.openshift.versions="v4.12-v4.14" | ||
LABEL com.redhat.openshift.versions="v4.14-v4.16" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this correct? In STO we didn't drop 4.12 in the Dockerfile https://github.com/infrawatch/service-telemetry-operator/pull/628/files#diff-1bdd52a34bf3a3abe6a623c0296503ce293c3a2c7ebdf65e8290b282d4574b9cR16 I have a hunch this is the correct version if we don't intend to support 4.12 anymore, in which case perhaps the STO one needs to change? I think it was simply expanded because we still have 4.12 testing happening and Emma expanded it to bring 4.16 online. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch. Yes, I think we should drop 4.12 from STO. Keeping it doesn't hurt, but we want to move from it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We already dropped upstream CI https://github.com/infrawatch/service-telemetry-operator/blob/master/.zuul.yaml, so I don't see a point of keeping it. I will propose a change for STO. |
||
LABEL com.redhat.delivery.backport=false | ||
|
||
LABEL com.redhat.component="smart-gateway-operator-bundle-container" \ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
properties: | ||
- type: olm.maxOpenShiftVersion | ||
value: "4.14" | ||
value: "4.16" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we update this base? I just spotted it with SGO, and may have missed with STO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was updated in STO already :) infrawatch/service-telemetry-operator@27cb54a