add keylime-poc part 1: docker compose and agent with swtpm #105
+890
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
2 times, most recently
from
b625285 to
b66d859
Compare
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
5 times, most recently
from
dd6115b to
fb4d945
Compare
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
from
7286735 to
a797271
Compare
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
from
a797271 to
2f605c5
Compare
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
from
2f605c5 to
1a796f8
Compare
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
7 times, most recently
from
f92ddee to
475db7a
Compare
Make a Proof of Concept of Keylime is k8s cluster. This part 1 is adding Keylime in Docker Compose. This doubles as the keylime service part in part 2, where agent(s) move to k8s. Agent image is having SWTPM module built-in, so this environment is portable across machines, regardless of their TPM chip or lack there of. This POC is needed as the concept of having Keylime Tenant/Verifier/Registrar outside k8s cluster, but Keylime Agent in k8s cluster and being accessed via Ingress/LoadBalancer IP, is something Keylime maintainers did not think originally as a use-case. This has several issues with the current design, and while there is a proposal/ study for changing from "pull model" to "push model", it is miles away and this POC tries to find out the minimal changes needed to make the current model work for this use case. Signed-off-by: Tuomo Tanskanen <[email protected]>
tuminoid
force-pushed
the
tuomo/add-keylime-poc
branch
from
475db7a to
83e5a2e
Compare
tuminoid
changed the title
|
/cc @Rozzii @lentzi90 @kashifest Let's merge part 1 with compose + agent, part 2 will be k8s part. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make a Proof of Concept of Keylime is k8s cluster.
This part 1 is adding Keylime in Docker Compose. This doubles as the keylime service part in part 2, where agent(s) move to k8s. Agent image is having SWTPM module built-in, so this environment is portable across machines, regardless of their TPM chip or lack there of.
This POC is needed as the concept of having Keylime Tenant/Verifier/Registrar outside k8s cluster, but Keylime Agent in k8s cluster and being accessed via Ingress/LoadBalancer IP, is something Keylime maintainers did not think originally as a use-case. This has several issues with the current design, and while there is a proposal/ study for changing from "pull model" to "push model", it is miles away and this POC tries to find out the minimal changes needed to make the current model work for this use case.