Fix Workload Attestation failure regression #47261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ryanclark
approved these changes
Oct 7, 2024
tigrato
approved these changes
Oct 7, 2024
public-teleport-github-review-bot
bot
removed request for
timothyb89 and
capnspacehook
|
@strideynet See the table below for backport results.
|
This was referenced Oct 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@rcanderson23 encountered an issue where Workload ID was no longer issuing credentials after upgrading to a version which contained Kubernetes Workload Attestation. It turns out my PR for Kubernetes Workload Attestation unintentionally made a failure to determine the PID of a connecting workload a hard failure. This PR restores that as a soft failure and tries to make this flow a little more readable.
changelog: Fixed error in Workload ID in cases where the process ID cannot be resolved.