Red Hat SSO session allows to use Sandbox registration service to guide user through Sandbox activation and work with the cluster trough the API end point proxy server. Those two things allows to configure sandbox kubernetes context using 'pipeline' service account. The main benefit of using service account is that the token for service account never changes.
Here is an implementation for sandbox integration in VSCode OpenShift Toolkit Extension
Red Hat SSO session allows to use Sandbox registration service to guide user through Sandbox activation and work with the cluster trough the API end point proxy server. Those two things allows to configure sandbox kubernetes context using 'pipeline' service account. The main benefit of using service account is that the token for service account never changes.
Here is an implementation for sandbox integration in VSCode OpenShift Toolkit Extension
https://private-user-images.githubusercontent.com/620330/343927172-e05717f5-039b-4029-9435-2317ba971a6b.mov?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk1MjY0OTMsIm5iZiI6MTcxOTUyNjE5MywicGF0aCI6Ii82MjAzMzAvMzQzOTI3MTcyLWUwNTcxN2Y1LTAzOWItNDAyOS05NDM1LTIzMTdiYTk3MWE2Yi5tb3Y_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjI3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyN1QyMjA5NTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hYzRmNGM0ZjRiM2Y2ZmNmNmRiNjgwODhiYjJiYmJhOTNiYzM5MzU1YzIzNGJjNWJmM2U4ZWUzMmJhZDE5ZGMxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.RPimc8G_iD5c2uKBWhHqk7mDTOWghhMU8n6-lI3H6WU