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

[TEP-0089] Enforce non-falsifiable provenance using SPIRE #6597

Open
9 of 10 tasks
jagathprakash opened this issue Apr 28, 2023 · 1 comment
Open
9 of 10 tasks

[TEP-0089] Enforce non-falsifiable provenance using SPIRE #6597

jagathprakash opened this issue Apr 28, 2023 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jagathprakash
Copy link
Member

jagathprakash commented Apr 28, 2023

This is a tracking bug for the implementation of TEP-0089.

TEP-0089 is a proposal to enforce non-falsifiable provenance using SPIRE.

The PRs created to implement this issue are

  • PR-5039 [TEP-0089] - Spire Package
  • PR-5647 [TEP-0089] Apis to handle SPIRE signing and verification.
  • PR-5676 [TEP-0089] Modify entrypoint to sign the results.
  • PR-5902 [TEP-0089] Add a config map to support SPIRE initialization.
  • PR-6524 [TEP-0089] SPIRE for non-falsifiable provenance - IsSpireEnabled
  • PR-6527 TEP-0089: Refactor setting of "enforce-nonfalsifiability" feature flag
  • PR-6539 [TEP-0089] Add CSI volumes to the Pods which provide the SPIRE workload API
  • PR-6553 [TEP-0089] SPIRE for non-falsifiable provenance. Setup the test environment
  • PR-6627 [TEP-0089] Inject SpireControllerAPIClient into the Taskrun controller and reconciler.
  • PR-6782 [TEP-0089] Enable the signing and verification of TR results and the TR status
@jagathprakash jagathprakash added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 28, 2023
@jagathprakash jagathprakash changed the title Tracking bug for TEP-0089 Tracking issue for TEP-0089 Apr 28, 2023
@wlynch wlynch changed the title Tracking issue for TEP-0089 [TEP-0089] Enforce non-falsifiable provenance using SPIRE Apr 28, 2023
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue May 5, 2023
Inject SpireControllerAPIClient into the controller and the taskrun reconciler.

This commit is part of a series of PRs to implement TEP-0089.
The implementation of TEP-0089 is tracked in the issue [tektoncd#6597](tektoncd#6597).
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue May 9, 2023
Inject SpireControllerAPIClient into the controller and the taskrun reconciler.

This commit is part of a series of PRs to implement TEP-0089.
The implementation of TEP-0089 is tracked in the issue [tektoncd#6597](tektoncd#6597).
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue May 16, 2023
Inject SpireControllerAPIClient into the controller and the taskrun reconciler.

This commit is part of a series of PRs to implement TEP-0089.
The implementation of TEP-0089 is tracked in the issue [tektoncd#6597](tektoncd#6597).
@jerop jerop added this to the Pipelines v0.49 milestone May 16, 2023
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue May 18, 2023
…oller and the taskrun reconciler. It makes it available in these objects to be used for signing and verification of the taskrunResults and the taskrun object itself.

Before this change the spireAPIController object was not injected into the taskRun and as such SPIRE was not available to be used.

After this change,
- spireApiController will be available to be used by the pipeline controller and the taskrun object.
- The spireApiController will be update with the spire config whenever the config changes.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
Inject SpireControllerAPIClient into the controller and the taskrun reconciler.

This commit is part of a series of PRs to implement TEP-0089.
The implementation of TEP-0089 is tracked in the issue [tektoncd#6597](tektoncd#6597).
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue May 18, 2023
…r and reconciler

This PR injects the spireControllerAPIClient into the pipelines controller and the taskrun reconciler. It makes it available in these objects to be used for signing and verification of the taskrunResults and the taskrun object itself.

Before this change the spireAPIController object was not injected into the taskRun and as such SPIRE was not available to be used.

After this change,
- spireApiController will be available to be used by the pipeline controller and the taskrun object.
- The spireApiController will be update with the spire config whenever the config changes.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
Inject SpireControllerAPIClient into the controller and the taskrun reconciler.

This commit is part of a series of PRs to implement TEP-0089.
The implementation of TEP-0089 is tracked in the issue [tektoncd#6597](tektoncd#6597).
tekton-robot pushed a commit that referenced this issue May 19, 2023
…r and reconciler

This PR injects the spireControllerAPIClient into the pipelines controller and the taskrun reconciler. It makes it available in these objects to be used for signing and verification of the taskrunResults and the taskrun object itself.

Before this change the spireAPIController object was not injected into the taskRun and as such SPIRE was not available to be used.

After this change,
- spireApiController will be available to be used by the pipeline controller and the taskrun object.
- The spireApiController will be update with the spire config whenever the config changes.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue #6597 SPIRE for non-falsifiable provenance.
Inject SpireControllerAPIClient into the controller and the taskrun reconciler.

This commit is part of a series of PRs to implement TEP-0089.
The implementation of TEP-0089 is tracked in the issue [#6597](#6597).
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 6, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 13, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 13, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 19, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 19, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 19, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 19, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 19, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
jagathprakash added a commit to jagathprakash/pipeline that referenced this issue Jun 19, 2023
…TR status.

This PR enables the signing and verification of TR results and TR status.

Before this change the spireAPIController object was injected into the TR reconciler but it was not used.

After this change,
- At the start of every reconcile run, the reconciler will verify if the signature on the status can be verified, else it will error out.
- At the end of every reconcile run, the reconciler will sign the status and add it as an annotation.
- When TR results are read from the termination message and converted into TR results, they will be verified.

This commit is part of a series of PRs to implement TEP-0089. The implementation of TEP-0089 is tracked in the issue tektoncd#6597 SPIRE for non-falsifiable provenance.
@jerop jerop removed this from the Pipelines v0.52 milestone Sep 5, 2023
@jerop jerop added this to the Pipelines v0.53 milestone Sep 5, 2023
@pritidesai
Copy link
Member

Lets clear the milestone for now, we can bring it back if someone volunteers or we find someone to work on this. We do not have any owner at this time.

@pritidesai pritidesai removed this from the Pipelines v0.53 LTS milestone Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

6 participants