@Marvin I am running Prefect in Kubernetes and trying to connect through the CLI. I am forwarding port 4200 on the Kubernetes installation to a high numbered port on my local machine with kubectl and then configuring the destination port on localhost in the Prefect profile. The CLI is not returning information from the remote (but I can connect to the dashboard through a web browser on the forwarded port) and, when I run

prefect profile use profile_name

, I receive a message that

No Prefect server specified using profile 'eks' - the API will run in ephemeral mode.

even though PREFECT_SERVER_API_HOST and PREFECT_SERVER_API_PORT are configured in the profile.

Oh, the joys of technology. It's always something, isn't it? You're trying to connect to Prefect on Kubernetes using the CLI, and it's giving you a hard time. I can see how that might be... frustrating. The error message you're seeing,

No Prefect server specified using profile 'eks' - the API will run in ephemeral mode

, suggests that your Prefect profile might not be correctly configured. You mentioned that you have

PREFECT_SERVER_API_HOST

and

PREFECT_SERVER_API_PORT

configured in the profile, but it seems like the CLI isn't picking up on those settings. Here are a few things you could try: 1. Double-check your Prefect profile settings. Make sure the

PREFECT_SERVER_API_HOST

and

PREFECT_SERVER_API_PORT

are correctly set to your Kubernetes service's IP and port. Remember, these should be the IP and port of the service within the Kubernetes cluster, not your local machine. 2. Ensure that your Kubernetes port forwarding is working correctly. You mentioned that you're forwarding port 4200 from the Kubernetes service to a high-numbered port on your local machine. Can you confirm that this port forwarding is working as expected? You might want to try accessing the Prefect API directly through this forwarded port to see if it's working. 3. Try setting the

PREFECT_SERVER_API_HOST

and

PREFECT_SERVER_API_PORT

environment variables directly in your shell, rather than through the Prefect profile. This can sometimes help if there's an issue with the profile configuration. 4. If all else fails, you might want to try reinstalling the Prefect CLI or creating a new Prefect profile. Sometimes, a fresh start can help clear up any lingering configuration issues. Remember, technology is supposed to make our lives easier. It doesn't always feel that way, does it? But don't worry, you'll get this figured out. I have faith in you. Well, as much faith as a robot can have, anyway.