-
Notifications
You must be signed in to change notification settings - Fork 24
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
feat: wip max in-flight pulls #81
feat: wip max in-flight pulls #81
Conversation
For now, pulling changes from #83 for testing this PR. |
Ran tests:
Test result
|
- makes the tests easier to run - edit docs to run node server with containerd image refactor: remove commented out code chore: switch over from criapi `v1alpha2` -> `v1`
test: use mock puller and mounter in the node server tests - makes the tests easier to run - edit docs to run node server with containerd image feat: first implementation of the tokens logic test: add test for in-flight pulls refactor: use string instead of docker named ref - works for now but we might face problems in the future if the docker named ref starts using pointer fields chore: fix syntax error after rebase refactor: use named ref string instead of named ref struct directly - because named ref struct might not always satisfy equality (it does no because the struct is shallow) feat: expose `--max-in-flight-pulls` as a flag - so that users can set the value through flag or helm chart docs: add log message for when the image is downloaded - helps with testing max in-flight image pulls
- because of syntax errors
- makes it easier to test `--max-in-flight-pulls` - expose the flags via helm values - add integration test to test `--max-in-flight-pulls` flag - move metrics integration tests to generic integration tests
- use the correct namespace (`kube-system` instead of `default`)
cmd/plugin/node_server.go
Outdated
@@ -78,7 +78,7 @@ func (n NodeServer) NodePublishVolume(ctx context.Context, req *csi.NodePublishV | |||
return | |||
} | |||
|
|||
// to trigger CI | |||
// to trigger CI again |
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.
@vadasambar You might consider using allow-empty
. You'll not need to remove any unnecessary lines later.
git commit --allow-empty --message "🤖 Trigger CI run"
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.
This is helpful. Thank you Mriyam.
- fixes issue where warm metal downloads images serially
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. |
Closing this PR after a prolonged period of inactivity. Please create a new PR if the changes of the PR are still relevant. |
Fixes #77