Rafael Leal
Rafael Leal
**Actual behavior** I'm using Tekton+EKS so we use kaniko to build images. A clear and concise description of what the bug is. We started to see an error like this:...
# Expected Behavior When a TaskRun can't correctly mount the volume, it should fail. # Actual Behavior The TaskRun's remains "Running" with the message Pending until it eventually times out....
# Expected Behavior The `alpha` features become available # Actual Behavior The tekton-pipelines-controller crashed with this panic message: `fatal error: stack overflow`. I created a gist with the full stack...
## Context Currently, the body schema for the `:patch` action is empty, which doesn't allow any valid patch to be done. This happens because the swagger schema itself it's configured...
Currently, if I build and try to run it on OSX gives the following error: 
### Feature request `kube-state-metrics` has some metrics like `kube_pod_labels` and `kube_pod_info` which allow us much more flexibility while aggregating metrics for tasks. But, as far as I know, it doesn't...
# Changes Issue: https://github.com/tektoncd/pipeline/issues/6076 This PR tries to fix scenarios where in the same reconciliation cycle the PipelineRun status gets too big to be updated and the status is changed...
# Expected Behavior Tekton should be able to run PipelineRuns that are big or at least give a proper error. # Actual Behavior PipelineRun gets stuck in the same status...
## What is it? Some special functions like `filter`, `map`, `exists`, `all`. For example: ``` ["project1/text.txt", "project2/text.txt"].exists(t => t.startsWith("project1")) ; => true ``` ## Why? This would simplify a lot...
### Objective Better support for monitoring TaskRuns and PipelineRuns ### How A new abstraction that allows you to customize how the metrics will be exported. This way to can control...