-
Notifications
You must be signed in to change notification settings - Fork 41
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
Bump project version to v0.7.0 #62
Conversation
Signed-off-by: Christopher Desiniotis <[email protected]>
Signed-off-by: Christopher Desiniotis <[email protected]>
Upon further thought, we could name this release |
@@ -23,7 +23,7 @@ spec: | |||
serviceAccountName: nvidia-mig-manager-service-account | |||
containers: | |||
- name: nvidia-mig-manager | |||
image: nvcr.io/nvidia/cloud-native/k8s-mig-manager:v0.6.0-ubi8 | |||
image: nvcr.io/nvidia/cloud-native/k8s-mig-manager:v0.7.0-ubi8 |
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.
Not a blocking comment. But we should consider publishing ubi9 images at some point
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.
Do you mean that we need to replace the images?
Note that since we copy the mig-parted
executable from the container to the host, we want to ensure that we're using as low a base version as possible to avoid issues with GLIBC dependencies.
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.
I meant use ubi9
as the base image instead of ubi8
No description provided.