#518 [BUG] Improve ease of locally running flyteadmin integration tests Issue created by katrogan Describe the bug In short the current system for running integration tests locally on a user's machine lacks polish. It requires manual config tweaking, port-forwarding, etc. This should be investigated to see if it can be improved. Expected behavior A clear and concise description of what you expected to happen. Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☑︎ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other To Reproduce Steps to reproduce the behavior: 1. ... 2. ... Screenshots If applicable, add screenshots to help explain your problem. Environment Flyte component ☐ Sandbox (local or on one machine) ☐ Cloud hosted ☐ AWS ☐ GCP ☐ Azure ☐ Baremetal ☐ Other Additional context Add any other context about the problem here. flyteorg/flyte

#518 [BUG] Improve ease of locally running flyteadmin integration tests Issue closed as not planned by github-actions[bot] flyteorg/flyte