vmware / vmware/nsx-container-plugin-operator
Network CRD status update should take into account the actual NSX status
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 34
- Forks
- 28
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Currently the operator simply uses CIDRs in the network CRD to update the network CRD status.
However, more CIDRs can be specified in NCP configuration. These should be reported as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the Network CRD status update and how NCP configuration provides additional CIDRs, then compare that with the actual NSX status. Done means the Network CRD status reports CIDRs configured through NCP as well as those specified in the CRD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100