-
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
TEP-0127: Larger results using sidecar logs - feature flags and cluster-roles #5828
TEP-0127: Larger results using sidecar logs - feature flags and cluster-roles #5828
Conversation
497249c
to
3dfb2a8
Compare
The following is the coverage report on the affected files.
|
3dfb2a8
to
d7dda5d
Compare
/kind feature |
The following is the coverage report on the affected files.
|
d7dda5d
to
b583bbd
Compare
The following is the coverage report on the affected files.
|
b583bbd
to
bcd63f7
Compare
The following is the coverage report on the affected files.
|
/retest |
bcd63f7
to
ef4b817
Compare
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.
@chitrangpatel thank you for splitting up the PR!
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop 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 |
/lgtm |
pkg/apis/config/testdata/feature-flags-invalid-max-result-size-bad-value.yaml
Show resolved
Hide resolved
pkg/apis/config/testdata/feature-flags-invalid-max-result-size-too-large.yaml
Show resolved
Hide resolved
{ | ||
expectedConfig: &config.FeatureFlags{ | ||
EnableAPIFields: "stable", | ||
EmbeddedStatus: "full", |
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.
Is there a specific reason that this is full embedded status here instead of the default?
Changes
Prior to this, we were extracting results from tasks via the termination messages which had a limit of only 4 KB per pod. If users had multiple results outputted by a task then they would have to share the 4KB limit.
We now run a dedicated sidecar that has access to the results of all the steps. This sidecar prints out the result and its content to stdout. The logs of the sidecar are parsed by the taskrun controller and the results updated instead of termination logs. We enforce an upper limit of 4KB per result (configurable) but there is no overall cumulative limit shared the results (users can have as many 4KB (or as configured) results as they desire).
This PR addresses the installation related changes of TEP-0127 - feature-flags and cluster-roles (see #5695).
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes