Registry1 flavor is currently untested on nightly eks test

[zack-is-cool]

Describe what should be investigated or refactored

Ideally, the registry1 flavor would be tested in the nightly eks tests. Bonus points if the eks tests occur in govcloud as this package is currently used in AWS Govcloud on EKS.

Links to any relevant code

Nightly eks test

https://github.com/defenseunicorns/uds-core/blob/main/.github/workflows/test-eks.yaml

Related issues

https://github.com/defenseunicorns/uds-core/issues/213

edit: updated w/ correct info

[mjnagel]

Just to clarify - registry1 is tested on all PRs and before release, but only on k3d. The missing part is nightly (EKS) tests of registry1.

[mjnagel]

This should be relatively quick to add to our EKS workflow. Some pointers for this:

• Add a matrix for flavor (similar to the existing k3d PR tests)
• Pass the flavor into the create task with --set to ensure we create the necessary package (this is used in the task during package create)
• Nice to have - also add unicorn flavor to the matrix, setup/auth to cgr should be handled for you already so this should be a simple addition