Gabe Montero
Gabe Montero
# Changes collaborating with @khrm here is an augmented version of https://github.com/tektoncd/pipeline/pull/7893 Fixes https://github.com/tektoncd/pipeline/issues/7909 During both sides of remote resolution (core controller and resolver) typically transient kubernetes errors were being...
# Changes Back when implementing https://github.com/tektoncd/pipeline/pull/6744 for https://github.com/tektoncd/pipeline/issues/6631 we failed to realize that with k8s quota policies being namespace scoped, knowing which namespace the throttled items were in could have...
# Expected Behavior the controllers in 'tekton-pipelines-remote-resolvers' and then consumer controllers in 'tekton-pipeline-controller' should retry on well known transient k8s errors like timeouts/deadlines-exceeded # Actual Behavior right now permanent errors...
### Feature request Back when implementing https://github.com/tektoncd/pipeline/pull/6744 for https://github.com/tektoncd/pipeline/issues/6631 we failed to realize that with k8s quota policies being namespace scoped, knowing which namespace the throttled items were in could...
### Feature request So by adding some affinity policies to the watcher deployment (I'll create a separate issue/PR for that), my team is on path to properly launching the watcher...
rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED # Changes Fixes https://github.com/tektoncd/results/issues/720 alternative to https://github.com/tektoncd/results/pull/712 with regard to still addressing the goroutine/memory leak, swtiching from the tkn client to k8s client, but with the...
# Expected Behavior UpdateLog calls from the watcher should not suffer from accidental canceled context errors when the timing is as such that contexts used for the UpdatLog call are...
### Feature request As a consumer of tekton results, the project we are working on employs use of [Checkov](https://www.checkov.io/) to help monitor cloud infrastructure configuration for various best practices. In...
Started seeing some overlap in validation individual PRs are doing in this repo with what is already done is spots like https://github.com/shipwright-io/build/blob/main/pkg/validate/ Do we just halt / remove doing analogous...
See https://github.com/cli/cli/pull/8824#issuecomment-2009670427 for the essential description now. Quick example output snippet: ``` ALIASES gh codespace ls gh cs ls FLAGS -q, --jq expression Filter JSON output using a jq expression...