Srijoni Biswas
Srijoni Biswas
> what is the status with Kserve? Some of the kserve images also have massive CVEs @juliusvonkohout I have a [PR](https://github.com/kserve/kserve/pull/4358) with all the changes in. I have one lgtm....
I understand from [this](https://github.com/kserve/kserve/blob/master/.github/workflows/helm-publish.yml#L33) kserve images are currently configured to ghcr but are there any other place where the change from docker -> ghcr needs to be updated?
@spolti @terrytangyuan I added this to the KFSevering Working group agenda to discuss this further.
> Do we plan to eventually move all the images to ghcr? Maybe we should given the rate limiting being in place from docker end. Here is the announcement :...
@sivanantha321 Updated all the images, please kindly help review it. Thank you.
> @biswassri Please run the `make precommit` Done!
@sivanantha321 Some of the pipelines are failing due to timeout errors. E2E tests with the components are failing with different errors. Is this related? Or can you please help identify...
> @biswassri You need to replace `ghcr.io/` in the image name just like we are replacing `latest` tag with git commit sha [here](https://github.com/kserve/kserve/blob/master/test/scripts/gh-actions/update-test-overlays.sh) @sivanantha321 do you suggest added the new...
@RobertSamoilescu Any thoughts? Or any suggestion on who I should reach out to about this?