Closed orfeas-k closed 10 months ago
Interesting finding is that the kserve-integration
UAT from main
branch PASSED when deployed latest/edge
bundle.yaml file. Will rerun UATs from track/1.7 on bundle 1.7/stable
. The only difference between the UATs branches is this bugfix PR, but when upgrading from Kserve 0.10 -> 0.11, we also switched from raw-deployment
mode to serverless
, which could affect the K8s services created by Kserve.
As noted in https://github.com/canonical/kserve-operators/issues/148 and in the notebook's PR https://github.com/canonical/charmed-kubeflow-uats/pull/10
This only works with Serverless deployment mode at the moment
Thus, the above behavior is expected since we ran this with CKF 1.7 that deploys Kserve in RawDeployment
mode. We will close this issue but we will need to investigate more https://github.com/canonical/kserve-operators/issues/148 in order to understand:
RawDeployment
RawDeployment
or switch to Serverless in 1.7 as well, to get KServe workingReopening. We will keep this open until we update the kserve-integration
UAT notebook with a requirement-note that this works only serverless
mode of Kserve.
Running the kserve-integration UAT notebook from
main
branch on a self-hosted runner fails with the following traceback of HTTPConnection errors:The
Name or service not known
probably means that something failed during DNS resolutionEnvironment
Logs