Inject Serving images#1630
Conversation
|
Serving tests faiure: |
|
/retest |
|
|
/retest |
1 similar comment
|
/retest |
|
/hold |
| wget --no-check-certificate "$url" -O "$target_file" | ||
|
|
||
| if [[ ${KNATIVE_SERVING_MANIFESTS_DIR} = "" ]]; then | ||
| url="https://raw.githubusercontent.com/skonto/serving/${branch}/openshift/release/artifacts/$index-$file" |
There was a problem hiding this comment.
After we merge the PR at the openshift/serving repo we can then change back to https://raw.githubusercontent.com/openshift/knative-serving/${branch}/openshift/release/artifacts/$index-$file
| serving_artifacts_branch: image_injection_1.3 | ||
|
|
There was a problem hiding this comment.
nit: maybe group this with dependencies.serving as put them closer to each other?
| wget --no-check-certificate "$url" -O "$target_file" | ||
|
|
||
| if [[ ${KNATIVE_SERVING_MANIFESTS_DIR} = "" ]]; then | ||
| url="https://raw.githubusercontent.com/skonto/serving/${branch}/openshift/release/artifacts/$index-$file" |
There was a problem hiding this comment.
nit: if we align the serving repo first we can point to the proper midstream branch instead of yours, meaning we can merge your branch in serving first, and then we can just use the final one here.
This would simplify the review of the deleted patches making sure that what we're removing here is added to the serving repo.
| git apply "$root/openshift-knative-operator/hack/001-serving-namespace-deletion.patch" | ||
| # When openshift-knative/serving uses this repo to run a job (eg. PR against openshift-knative/serving) it will use a minimum | ||
| # setup with net-kourier. Thus it will not use the release artifacts generated under openshift-knative-operator/cmd/kodata/knative-serving. | ||
| # Instead openshift-knative/serving uses its own generated ci manifests and sets KNATIVE_SERVING_TEST_MANIFESTS_DIR. |
There was a problem hiding this comment.
| # Instead openshift-knative/serving uses its own generated ci manifests and sets KNATIVE_SERVING_TEST_MANIFESTS_DIR. | |
| # Instead openshift/knative-serving uses its own generated ci manifests and sets KNATIVE_SERVING_TEST_MANIFESTS_DIR. |
| diff --git a/openshift-knative-operator/cmd/operator/kodata/knative-serving/1.3.0/2-serving-core.yaml b/openshift-knative-operator/cmd/operator/kodata/knative-serving/1.3.0/2-serving-core.yaml | ||
| index 4f7af33d..4a5ce15f 100644 | ||
| --- a/openshift-knative-operator/cmd/operator/kodata/knative-serving/1.3.0/2-serving-core.yaml | ||
| +++ b/openshift-knative-operator/cmd/operator/kodata/knative-serving/1.3.0/2-serving-core.yaml |
There was a problem hiding this comment.
Great! Another step to the removal of versioned directories!
| @@ -1,31 +0,0 @@ | |||
| diff --git a/openshift-knative-operator/cmd/operator/kodata/knative-serving/1.3.0/2-serving-core.yaml b/openshift-knative-operator/cmd/operator/kodata/knative-serving/1.3.0/2-serving-core.yaml | |||
There was a problem hiding this comment.
I don't see this patch in https://github.com/skonto/serving/tree/image_injection_1.3/openshift/patches, maybe it's planned for later but I'd keep track of these removed patches.
There was a problem hiding this comment.
It is here: https://github.com/skonto/serving/tree/image_injection_1.3/openshift/release/manifest-patches.
Reason is that https://github.com/skonto/serving/tree/image_injection_1.3/openshift/patches only contains the patches for the ci yaml files. The release ones are there. This is because the Serving setup for ci tests (eg. when a PR is done at the openshift/knative-serving) repo is minimal. It is not the same one we have at the S-O side eg. no istio is used only kourier. For now the release manifests are downloaded in that new dir until we unify the process of testing and releasing.
There was a problem hiding this comment.
Ok, thanks!
One note on patches:
- https://github.com/skonto/serving/blob/image_injection_1.3/openshift/release/manifest-patches/001-serving-namespace-deletion.patch is based on a generated bundles, is there any reason for not doing something like this https://github.com/openshift-knative/eventing-kafka-broker/blob/2f16a913ea82e6b36d0ccc7e4eb5f5deea7c0f1b/openshift/release/generate-release.sh#L10-L11, that would remove the need to change
"serving.knative.dev/release: "v1.3.0"toserving.knative.dev/release: "v1.4.0"in the next release.
Similar comment on other patches since basing them on the origin of the final manifests would benefit from future changes.
There was a problem hiding this comment.
But that's not really relevant for this PR, just a thought
There was a problem hiding this comment.
Yeah we could do that I will take a note and do it when we merge the patches. As a side note https://github.com/skonto/serving/tree/image_injection_1.3/openshift/patches, contains also code patches in https://github.com/skonto/serving/blob/image_injection_1.3/openshift/release/manifest-patches it is only manifest patches as they are used in Serverless Operator.
|
/retest |
pierDipi
left a comment
There was a problem hiding this comment.
/hold
2 nits, they can be fixed later tho
/lgtm
/approve
| # setup with net-kourier. Thus it will not use the release artifacts generated under openshift-knative-operator/cmd/kodata/knative-serving. | ||
| # Instead openshift-knative/serving uses its own generated ci manifests and sets KNATIVE_SERVING_TEST_MANIFESTS_DIR. | ||
| # Extensive Serving testing is done at this repo only. For the latter we do use manifests under openshift-knative-operator/cmd/kodata/knative-serving which are fetched from the midstream | ||
| # repo. TODO: unify the artifacts at the mid stream repo. |
There was a problem hiding this comment.
I guess TODO is done?
| # repo. TODO: unify the artifacts at the mid stream repo. | |
| # repo. |
There was a problem hiding this comment.
Nope this is not done. Unifying means using the manifests from one place. Check my comment: #1630 (comment).
But we can remove that.
| git apply "$root/openshift-knative-operator/hack/001-serving-namespace-deletion.patch" | ||
| # When openshift-knative/serving uses this repo to run a job (eg. PR against openshift-knative/serving) it will use a minimum | ||
| # setup with net-kourier. Thus it will not use the release artifacts generated under openshift-knative-operator/cmd/kodata/knative-serving. | ||
| # Instead openshift-knative/serving uses its own generated ci manifests and sets KNATIVE_SERVING_TEST_MANIFESTS_DIR. |
|
/retest |
1 similar comment
|
/retest |
|
Nits done waiting for tests to pass. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierDipi, skonto The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold |
Uh oh!
There was an error while loading. Please reload this page.