Known issues

Here you find additional help, something went wrong, known issues or just get some information.

(Issue 1) In case your `Cloud Shell` session was closed

Setup the major environment variables we need in the workshop.

Solution: Follow these steps to setup the major environment variables we need in the workshop.

Step 1: Go back to the open browser tab the open Kubernetes Cluster in the IBM Cloud web console.

Now select Actions->Connect via CLI on the right-hand side.

In the new window you see all steps to access your Kubernetes Cluster in a terminal session. You can easily copy and paste the commands. We will use these commands later to access the Kubernetes cluster in the IBM Cloud Shell.

Step 2: Setup needed variable you maybe need in your lab

ROOT_FOLDER of your project

git clone https://github.com/IBM/cloud-native-starter.git
cd cloud-native-starter/security
ROOT_FOLDER=$(pwd)
echo $ROOT_FOLDER

MYCLUSTER your cluster name

export MYCLUSTER=YOUR-CLUSTER

INGRESSGATEWAYIP needed to create a DNS

export INGRESSGATEWAYIP=$(kubectl get svc -n istio-system | grep 'istio-ingressgateway' |  awk '{print $4}')
echo $INGRESSGATEWAYIP

INGRESSSECRET we use for Istio Ingress Gateway configuration

export INGRESSSECRET=export INGRESSSECRET=$(ibmcloud ks nlb-dns ls --cluster $MYCLUSTER | grep '0001' | awk '{print $5}')
echo $INGRESSSECRET

INGRESSURL we use to access for example the Cloud Native Starter application and Keycloak

export INGRESSURL=$(ibmcloud ks nlb-dns ls --cluster $MYCLUSTER | awk '/-0001./ {print $1}')
echo $INGRESSURL

(Issue 2) You can't access the Kubernetes Dashboard

When you open up your Kubernetes Dashboard from your cluster from the IBM Cloud WebConsole

and you get following error message:

It cloud be that you are logged on to two different IBM Cloud Accounts (your IBM Cloud account and the IBM Cloud workshop account) in different browser tabs.

Solution:

Just make sure you are signed in to the IBM Cloud Workshop account. To ensure this, just reload the tab on your browser and check the account. Then if you use the correct account it should work.