Fri, Apr 23
I noticed you are using a timestamp for the version, is this to ensure a unique key? We currently use semver with ORES but I could see how that could lead to naming collisions.
Sun, Apr 18
We chose to use S3 object storage over Swift, which comes with:
- Bucket names can have only lowercase letters, number, dots and hyphens. Typically names are in kebab-case, see AWS S3 bucket naming rules.
- Object key is the path to a file, a combination of the dir/subdir names and file name. It has more freedom on the choice of special characters (see AWS Creating object key names), although we can follow the bucket naming rules for simplicity.
- Object key can have tags. This can be useful as meta information, but it can't be used when accessing the objects as the object name has to be unique.
Wed, Apr 14
It should work but I've never tested it. Here is an example of how to configure the endpoint_url across all inferenceservices.
Apr 1 2021
Mar 31 2021
The service to service communication can be enhanced with a service mesh if we require for example security policies across the services of that cluster. By having Istio sidecar injection in a namespace, each pod will have an extra container with the envoy proxy that brings the access control, the logging, the tracing, etc in the services that these pods provide.
Mar 30 2021
Hey @elukey, this is the script we're using for e2e testing on kfserving community. It is using the most recent versions of Istio and knative, with their operators and having the sidecar injection disabled as per the requirement above.
Mar 20 2021
Mar 13 2021
Mar 9 2021
Also these large files are not used:
Feb 24 2021
Some thoughts on building a custom image per model.
Jan 31 2021
I've started a WIP PR which supports knative 0.20 and Istio 1.7.1 here.