FAQ / Issues during setup

Check the username and the development server IP and you are tunneling the right way from your local system.  

The command will look like this:

Make sure the authorized public/private keys are in the mentioned path in the ssh command. In the above example it is ads-srikar.  

You can access this from port mentioned locally that is: 20000. You'll be asked username and password which has been created. 

Make sure that you have generated ssh keys with the email that you have registered in bitbucket. (company email ending with @touchcast.com) 

Check that you have added the ssh keys to bitbucket account, under Settings > Personal Bitbucket settings > SSH keys.  

After that try to clone the repositories into your project folder. 

refer to this link: How To Generate ed25519 SSH Key   

Note that there's different kind of ssh keys be created. They ultimately serve the same purpose. What is ssh-keygen & How to Use It to Generate a New SSH Key?  

Refer to this documentation first. Kubernetes contexts 101 | Port forwarding  

Make sure you have requested for access from DevOps/Manager for the dev environment and shared the public key of your local system with the team.  

The -v tag would help give more information about the ssh connection to the jump server and what is failing.

Sometimes, there might be issues related to tunelling, in case of that, try to connect without creating a tunnel.  

In any other cases, reach out to DevOps to double check your access.

Make sure you have access to Kubernetes services in dev by going to azure portal, logging in with your company account.  

If you aren’t able to run the commands in this link: Kubernetes contexts 101 | Port forwarding , successfully, then try az login and login with your company account and authorize your device.  

Check the subscriptions that your account is enabled on. If it is "Free Trial", you can change it to the one you see in your portal. It would be something like "Pay-as-you-go". Take help from this link: Azure CLI doesn't recognize resource group  

After setting your subscription, try to run the get-credentials command and access k8 context.