-
Notifications
You must be signed in to change notification settings - Fork 42
executed the test_local from github action #447
Comments
with the latest approach, will try to create kubectl image with oidc-login plugin which uses for GitHub action
|
We can't use the oidc kubeconfigs with the CICD as the 2-factor is meant for humans (not automation). We would need a normal kubeconfig with sufficient permissions to perform these tasks |
yes, you are right, 2-factor required humans input, and it seems to enable in Live only, I never met in Dev required me to input the security code. I thought I could found some silent mode since dev landscape never asking input 2-factor code. however, OIDC required an access browser. I can't handle it when in Github action. now I am using the normal kubeconfig . as latest testing. It seems working well.
|
achieved execute test_local through GitHub action. which also covers more testing cases mention in form #393 (not include ssh testing and GCP feature as GCP workaround not working well now)however, it takes almost 10 mins. planning optimize it |
Describe the bug
I like to execute the test_local for e2e testing from GitHub action when any new commit pushed. the action which able to handle ssh testing in test_local and others eg
gardenctl
execution. and need feasible solution handle configuration file(garden dev kubeconfig)The text was updated successfully, but these errors were encountered: