Hi VSecM, this is SPIKE. #1275
Description
While the plans in v2.0.0 Realignment is an ambitious goal, the reality is without adequate time investment, it will take a very long time, and it will dramatically change the current VSecM architecture.
Instead of that, we can add features to VSecM to gradually move towards that goal.
Also, this does not have to be mutually exclusive:
While top-of-tree work continues, we can still freely ideate on the v2.x branch with the understanding that the branch may never be released. — That will help us re-use our findings in that branch on the top-of-tree gradually too.
This is one of those features.
We will deploy SPIKE along with VSecM.
SPIKE will be just "sitting there" in case anyone wants to use it.
So that as the next phase, we can swap VSecM backing store with SPIKE without changing the underlying API much.
This approach will
- Provide us speed,
- Will introduce minimal breaking changes
- keep the main branch active
To Introduce SPIKE, though, the first sub-task should be converting current VSecM container images to use Github Container Registry instead.
Luckily, there is already work done in the v2.0.0 branch for that that we can leverage.