The okteto-dev.sh script is an addon to the insights deployer repo, which allows users to convert configured deployments into development deployments, enabling realtime syncing of local code to the cluster with hot reloads/restarts and remote debugging.

The HBI host migration squad are the primary intended users of this script; however, we have seen some interest from the HBI team to begin using it for their purposes, and in general, it should be a useful tool to facilitate kessel adoption. As such, it's worth addressing minor issues that can give users a bad experience.

This task is to address some issues which have been found to affect first-time users, which have a slightly strange experience the first time they use the underlying okteto tool.

Issues:

1. Even though the user has checked out an .stignore file with the insights deployer, okteto still prompts the user to create one. If the user, who is unlikely to understand what they are being asked, selects "Y" (which I think is the default) a new, and problematic, .stignore file will be created that will cause issues with file syncing. We should stop this question being asked somehow.
2. The user is prompted to select a kubeconfig option to set as their default cluster/namespace for the okteto context. In practice, this results in selecting from a dropdown of a large number of past ephemeral clusters, and others, in which it is hard to find the current one. It's also unnecessary, because the okteto script actually never uses the okteto context – since it is always changing with each ephemeral deployment – and instead takes the namespace from the current context (oc project -q). We should prevent this from happening.

The above might be achieved by putting a "fake" okteto context in place, which will not be used, but which will suppress these questions.