-
Notifications
You must be signed in to change notification settings - Fork 12
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
NVIPAMPool CRD #24
NVIPAMPool CRD #24
Conversation
5efce78
to
1f21aef
Compare
4e6ec78
to
e7d8918
Compare
3964a63
to
caa0e7b
Compare
- Add CRD definition - Add Make targets - Add CR examples based on ConfigMap example Signed-off-by: Fred Rolland <[email protected]>
The controller part looks good for me. I added one extra comment about the node part. |
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.
a few minor comments, once addressed, LGTM from my side.
m.lock.Lock() | ||
defer m.lock.Unlock() | ||
m.reader = nil | ||
return m.poolByName |
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.
locking/unlocking doesnt help us much here
should we create a copy of the map ? or just drop mutex ?
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.
locking/unlocking doesnt help us much here
should we create a copy of the map
Why? We use mutex here to protect shared internal map from concurrent writes
Add IPPool controller, watching Pools. The IP range allocations are available on the CR status. Node controller triggers event on all Pools when Node is added/updated/deleted. Signed-off-by: Fred Rolland <[email protected]>
Move from watching Nodes object and read IP range from annotation, to watch IPPools objects and get Allocations from their Status. Signed-off-by: Fred Rolland <[email protected]>
In case the IP configuration ConfigMap exists: - Create IPPools CR according to config spec - Read Nodes ranges annotation - Populate the IPpools Status allocations - Clear Nodes ranges annotation - Delete ConfigMap In case an issue is preventing the migration flow, it can be skipped by setting the env var 'MIGRATOR_DISABLE_MIGRATION'. Signed-off-by: Fred Rolland <[email protected]>
Signed-off-by: Fred Rolland <[email protected]>
No description provided.