879c6a84a4
The new wrapper types should behave like the direct schedulerframework types for most purposes, so most of the migration is just changing the imported package. Constructors look a bit different, so they have to be adapted - mostly in test code. Accesses to the Pods field have to be changed to a method call. After this, the schedulerframework types are only used in the new wrappers, and in the parts of simulator/ that directly interact with the scheduler framework. The rest of CA codebase operates on the new wrapper types. |
||
|---|---|---|
| .. | ||
| api | ||
| utils | ||
| clusterstate.go | ||
| clusterstate_test.go | ||