Ngrok requires an authentication token, which brakes Kubefirst deployed via K3d. about kubefirst HOT 5 CLOSED

Indeed, it worked before; I have used it several times. Now that Ngrok has changed its usage rules or terms of the agreement (which I believe happened), an authentication token is mandatory. Once again, there is nothing wrong with Kubefirst, but as it uses it for K3d, we need to ensure Ngrok has what it needs.

from kubefirst.

Thanks for reporting this issue @agalue . It was working before, so we need to investigate. Maybe ngrok changed how their free tier is working token-wise.

from kubefirst.

@agalue thanks so much for the thorough assessment and detail on this issue. anyone reading along who needs a workaround, the one in this description works quite well as described.

i got this issue's fix merged yesterday so it'll go out in the next kubefirst release. the approach that we took was to expect our users to export an NGROK_AUTHTOKEN environment variable in their shell before running kubefirst k3d create. if they do, we'll include atlantis, and wire the authtoken into the vault secret as describe above. if the env var isn't exported, we'll remove atlantis from the registry of apps, and the k3d platform will simply not have that layer of IAC automation. we didn't want to force our users to create an ngrok account as a prerequesite step so we're basically making atlantis optional driven by env var presence.

from kubefirst.

Another workaround:

• Get auth and API tokens from ngrok
• Open Vault: https://vault.kubefirst.dev/
• Visit the atlantis-ngrok secret page
• Add NGROK_API_KEY and NGROK_AUTHTOKEN (note: no underscore in AUTHTOKEN)
• Delete the atlantis/ngrok container to restart it

If the right solution is we need to export ngrok env vars before the create, that isn't in the docs now as far as I can tell.

from kubefirst.

This has been release in v.2.3.9: more info on the new token at https://docs.kubefirst.io/k3d/quick-start/install#local-atlantis-executions-optional

from kubefirst.