-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: Update docs for release v0.11.0 #414
doc: Update docs for release v0.11.0 #414
Conversation
Related kserve#408 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Christian!
/LGTM
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: ckadner, rafvasq The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
- Add tags when pre-pulling images for FVT (`latest`, `v...`) - Pre-pull minio-examples and minio-dev-examples images for FVT - this is one reason for the frequent timeouts in the FVT setup nodes - predictor tests using minio-dev-examples - storage tests for PVC using minio-examples (non -dev-) - Update links to `modelmesh` environment variables - Update install-script and quickstart to clone `main` branch, adding note pointing to the most recent stable release, and re-including the self-signed cert flag (#364) - Update required minimum Kubernetes version to `1.23` (HPA `autoscaling/v2`) - Update modelmesh component-versions to `v0.11.0` - Update release-process docs with additional places where versions need to be replaced --------- Signed-off-by: Christian Kadner <ckadner@us.ibm.com> (cherry picked from commit e147d28)
Motivation
Several docs are still pointing to the previous release or are inconsistent in that the latest doc files from the
main
branch point to incompatible resources on the previousrelease-0.10
branch or tagged releasev0.10.0
.Modifications
latest
,v...
)modelmesh
environment variablesmain
branch, adding note pointing to the most recent stable release, and re-including the self-signed cert flag (doc: Remove cert flag from quickstart #364)1.23
(HPAautoscaling/v2
)v0.11.0
Result
Hopefully more consistent user experience when installing ModelMesh and more clarity for developers doing the release process.
FYI @rafvasq
Related #408