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

Do not require enable-api-fields=alpha for spire #6939

Merged
merged 1 commit into from
Jul 20, 2023

Conversation

lbernick
Copy link
Member

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:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/misc Categorizes issue or PR as a miscellaneuous one. labels Jul 18, 2023
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 18, 2023
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/config/feature_flags.go 92.6% 92.3% -0.3

Copy link
Member

@JeromeJu JeromeJu left a 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
Copy link
Member

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? 🤔

Copy link
Member Author

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

Copy link
Member

@afrittoli afrittoli left a 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

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 18, 2023
@afrittoli
Copy link
Member

/retest

@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/config/feature_flags.go 92.6% 92.3% -0.3

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.
@tekton-robot tekton-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 18, 2023
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/config/feature_flags.go 92.6% 92.3% -0.3

@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/config/feature_flags.go 92.6% 92.3% -0.3

@JeromeJu
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 18, 2023
@chuangw6
Copy link
Member

LGTM.

cc @jerop for visibility since https://github.com/tektoncd/pipeline/pull/6527/files added requirements of setting "enable-api-fields" to

Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@tekton-robot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 19, 2023
@jerop
Copy link
Member

jerop commented Jul 19, 2023

/hold

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 19, 2023
@jerop
Copy link
Member

jerop commented Jul 19, 2023

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

@lbernick
Copy link
Member Author

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.

@vdemeester
Copy link
Member

/lgtm

@jagathprakash
Copy link
Member

/lgtm

@tekton-robot
Copy link
Collaborator

@jagathprakash: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

@jerop
Copy link
Member

jerop commented Jul 20, 2023

/unhold

thanks for reviewing @jagathprakash 🙏🏾

@tekton-robot tekton-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 20, 2023
@tekton-robot tekton-robot merged commit f5b1a3e into tektoncd:main Jul 20, 2023
2 checks passed
@JeromeJu JeromeJu mentioned this pull request Jul 24, 2023
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants