-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Do not require enable-api-fields=alpha for spire #6939
Conversation
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @lbernick !
@@ -64,7 +64,7 @@ When a TaskRun is created: | |||
## Enabling TaskRun result attestations | |||
|
|||
To enable TaskRun attestations: | |||
1. Make sure `enforce-nonfalsifiability` is set to `"spire"` and `enable-api-fields` is set to `"alpha"` in the `feature-flags` configmap, see [`install.md`](./install.md#customizing-the-pipelines-controller-behavior) for details | |||
1. Make sure `enforce-nonfalsifiability` is set to `"spire"`. See [`additional-configs.md`](./additional-configs.md#customizing-the-pipelines-controller-behavior) for details |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: It looks like that the enforce-nonfalsifiablity
is neither set in additonal-configs/customizing-the-pipelines-controller-behavior
section, is it WIP? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, spire is still non-functional
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @lbernick - Spire is not controlled by the user via API - it should never have been an API flag, only a behavioural one.
/lgtm
/retest |
The following is the coverage report on the affected files.
|
Prior to this commit, enabling spire support also required setting "enable-api-fields" to alpha. "enforce-nonfalsifiability" is the only behavioral feature flag that also requires setting "enable-api-fields" to alpha, even though it is not the only behavioral feature flag in an alpha state. This commit removes the requirement that cluster operators set enable-api-fields to alpha in order to use spire. In addition to creating a consistent approach among behavioral feature flags, this will allow cluster operators to opt into spire without having to opt into all alpha API fields. Note: Spire support is not yet functional.
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
LGTM. cc @jerop for visibility since https://github.com/tektoncd/pipeline/pull/6527/files added requirements of setting "enable-api-fields" to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afrittoli, JeromeJu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
This change was introduced in https://github.com/tektoncd/pipeline/pull/5902/files#r1086050834 following a discussion between @bobcatfish and @jagathprakash so it'd be great to hear from them -- this change sgtm @chuangw6 https://github.com/tektoncd/pipeline/pull/6527/files was only refactoring the implementation, it didn't make any functional changes |
Thanks for the additional context! @bobcatfish and @jagathprakash aren't actively working on OSS tekton anymore, and @chuangw6 is taking over spire work and has given a LGTM. I'll reach out to the two of them, but I think it makes the most sense to evaluate this change based on the reasons given in the commit message. It looks like the linked conversation was more about returning an error instead of silently failing when enable-api-fields was not set to alpha, rather than the decision to couple the two flags in the first place. |
/lgtm |
/lgtm |
@jagathprakash: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/unhold thanks for reviewing @jagathprakash 🙏🏾 |
Prior to this commit, enabling spire support also required setting "enable-api-fields" to alpha. "enforce-nonfalsifiability" is the only behavioral feature flag that also requires setting "enable-api-fields" to alpha, even though it is not the only behavioral feature flag in an alpha state.
This commit removes the requirement that cluster operators set enable-api-fields to alpha in order to use spire.
In addition to creating a consistent approach among behavioral feature flags, this will allow cluster operators to opt into spire without having to opt into all alpha API fields.
Note: Spire support is not yet functional.
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes