Update stable to v2.7.0 #723
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
remove unncessary release test gh workflow
Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
downgrade upload-artifact
Replace boto3 with numpy
Add support for using route or service as target endpoints in the test suite
This will include all the changes from the kfp 2.2.0 release Signed-off-by: Ricardo M. Oliveira <rmartine@redhat.com>
Accomodate changes for KFP 2.2 upgrade
Added secrets::list permissions to pipeline runner
Signed-off-by: Giulio Frasca <gfrasca@redhat.com>
Co-authored-by: Francisco Arceo <farceo@redhat.com>
Reuse WaitFor function to ensure DSPA is ready
The DSP apiserver implements TLS by relying on the OpenShift service cert signer. In order to get this to work nicely with our openshift-oauth sidecar, we set the Kubernetes service as the upstream for the oauth container. This means that all incoming traffic to DSP goes like this: `client -> DSP service -> DSP oauth -> DSP service -> DSP apiserver` DSP oauth and DSP apiserver are in the same pod. We haven't explicitly created a NetworkPolicy to allow that, but it works on AWS and OpenStack-based clusters. For some yet to be determined reason, it doesn't work on IBM / Calico / Secure-By-Default clusters. Add a NetworkPolicy entry to allow the DSP pod to talk to itself on 8888 and 8887. This fixes the issue where DSP(oauth) can't talk to DSP(apiserver) via the service (that fronts both containers / the pod). Fixes: https://issues.redhat.com/browse/RHOAIENG-14571 Signed-off-by: Greg Sheremeta <gshereme@redhat.com>
Signed-off-by: Ricardo M. Oliveira <rmartine@redhat.com>
…-traffic-np fix: add NetworkPolicy for DSP apiserver pod self traffic
Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
update compatibility doc for 2.7
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
A new image has been built to help with testing out this PR: To use this image run the following: cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/723/head
git checkout -b pullrequest 998859f4b22bbbbb0a52adaf271f1037c978ba9d
oc new-project opendatahub
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-723"More instructions here on how to deploy and test a Data Science Pipelines Application. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update stable to v2.7.0