What follows is a list of technical debt that was incurred for RHEL-AI GA.
[ ] Investigate if aws string OK vs aws securestring via KMS for the runner's tokens
[ ] For now, RHEL-AI self-hosted gitlab runner infrastructure lives in the platform-engineering AWS account, because the Instructlab one does not have access to downstream resources, and we anticipate that we will need those (torch fork, etc.)
[ ] move these once we have configured downstream resource access on Ilab account and remove them from pe account
[ ] Infrastructure live changes
[ ] infrastructure live users are hard coded to liora, this should be dynamic based on the user running the command in the devcontainer
[ ] tfvars file in infrastructure live, should not have a dependency on hardcoded secrets
[ ] no ci that currently runs here in infrastructure live, configure tests for tf lint + other to run on pr
What follows is a list of technical debt that was incurred for RHEL-AI GA.
aws
string OK vs aws securestring via KMS for the runner's tokensRHEL-AI
self-hosted gitlab runner infrastructure lives in theplatform-engineering
AWS account, because theInstructlab
one does not have access to downstream resources, and we anticipate that we will need those (torch fork, etc.)pe
accountdevcontainer
cc @lmilbaum