Origin to/from Kube conversions for SAR
For example, origin SAR scopes can be translated to kube SAR extras.
Full round trip conversion may not be possible.
I (Mo) do not think they are fully convertible. Our SAR stuff defaults the namespace and user to the current if not given, kube requires it. Kube SAR also has
NonResourceAttributesandSubresourcewhich we do not seem to have. I am also not sure if kube'sExtraand ourScopescan be round tripped without losing data.
I planned on simply removing it but I was not sure if the origin SAR stuff even handled
NonResourceAttributes. While bothResourceAttributesandNonResourceAttributescannot be specified together, the origin stuff does have a.Pathso I feel like that should be used at some point.
xref: #13128
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
/unassign
@stlaz @sttts @mfojtik