Added signal handling in SidecarLog results to support Kubernetes-native sidecar functionality #9095
      
        
          +404
        
        
          −0
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Changes
In the native Kubernetes sidecar model, sidecars are implemented as init containers with a
RestartPolicy: Always, which means they run for the entire duration of the pod's lifecycle. However, the current Tekton sidecar log results implementation doesn't account for this behavior and exits after processing results, causing the container to restart repeatedly.This PR enhances the sidecarlogresults binary to support Kubernetes native sidecars by:
-kubernetes-sidecar-modeflag that, when enabled, prevents the sidecar from exiting after processing resultsA sample pipelineRun with DinD and task results:
Before:
After:
/kind bug
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