EAS api implentation#1411
Conversation
122a630 to
75a5c7a
Compare
b07abca to
fdceca9
Compare
f740a67 to
99c39b7
Compare
b16b2e0 to
476c66d
Compare
de62c72 to
e668134
Compare
e668134 to
f35c674
Compare
7335184 to
59a983e
Compare
06895a8 to
e3746a6
Compare
5d72928 to
2aa5983
Compare
3ed236e to
941fd6e
Compare
941fd6e to
8f5de94
Compare
|
@jianjuns @dantingl this 2 values are used to get values from vpc network config CR, the tags are used in previous release to set values between wcp svc and nsx-operator reconciler. i am not using this value to add annotation to CR, so this tag could not be changed, that would involve code change on both wcpsvc side and nsx-operator side and not related to this feature. |
3a295fb to
a2e948a
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1411 +/- ##
==========================================
+ Coverage 77.02% 77.47% +0.44%
==========================================
Files 156 168 +12
Lines 22048 23046 +998
==========================================
+ Hits 16983 17854 +871
- Misses 3859 3976 +117
- Partials 1206 1216 +10
🚀 New features to boost your workflow:
|
| - ipblockusages | ||
| - subnetippools | ||
| - subnetdhcpserverstats | ||
| verbs: ["get", "list"] |
There was a problem hiding this comment.
These APIs should only have GET
There was a problem hiding this comment.
per one pager, ipblockusage and vpcipaddressusage support list.
There was a problem hiding this comment.
If that, you should add ipblockusage and vpcipaddressusage for get/list
and move subnetippools and subnetdhcpserverstats for get
| "github.com/vmware-tanzu/nsx-operator/pkg/eas/storage" | ||
| ) | ||
|
|
||
| // ── VPCIPAddressUsage ──────────────────────────────────────────────────────── |
There was a problem hiding this comment.
it's better to move each api to an individual file
They are annotations on VPCNetworkConfig CR or not? Could you add some code comments before each to explain how they are used? |
The full resolution chain for any namespace is: Namespace has annotation vpc_network_config=? this logic is defined from the init version to scan VPCNetworkConfiguration. will add comments on function to explain how this annotation is used. |
1d8d813 to
79da0ff
Compare
1. add a new eas service in nsx-operator 2. register eas service to k8s api server 3. start a http service on 9553 port 4. add eas service implentations for ip usages api yamls
79da0ff to
47fed3d
Compare
|
|
||
| // Per-resource table column definitions for kubectl Table format. | ||
| var ( | ||
| vpcIPUsageColumns = []metav1.TableColumnDefinition{ |
There was a problem hiding this comment.
please also move table to the corresponding API file and merge the logic in one file
add EAS api implementation
Testing Done: