Skip to content
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

Tests for key manager upgrades #2517

Closed
kostko opened this issue Jan 6, 2020 · 0 comments · Fixed by #2920
Closed

Tests for key manager upgrades #2517

kostko opened this issue Jan 6, 2020 · 0 comments · Fixed by #2920
Assignees
Labels
c:keymgmt Category: key management c:testing Category: testing

Comments

@kostko
Copy link
Member

kostko commented Jan 6, 2020

Depends on #2516.

We should add E2E tests for key manager runtime upgrades (without production keys).

The process of upgrading the KM is the following:

  • First make sure an initial key manager is registered and operational.
  • Build an upgraded key manager runtime enclave (anything which changes MRENCLAVE should be fine).
  • Update the key manager policy to include the MRENCLAVE for the new runtime and wait for the policy to propagate.
  • Leave old key manager nodes running.
  • Spin up new key manager nodes with upgraded enclave.
  • Wait for the key manager nodes to replicate the master secret.
  • Verify that the key manager nodes work.
  • Take down old key manager nodes.
  • Verify that the key manager nodes work.
@kostko kostko added c:testing Category: testing c:keymgmt Category: key management labels Jan 6, 2020
@kostko kostko assigned Yawning and unassigned tjanez Apr 13, 2020
@ptrus ptrus assigned ptrus and unassigned Yawning May 12, 2020
@ptrus ptrus mentioned this issue May 18, 2020
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:keymgmt Category: key management c:testing Category: testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants