In some cases, you might be trying to create a new Konvoy cluster in AWS using the Kommander UI, and notice that it gets stuck and eventually fails.
In this case, you will want to check the logs of the "konvoy-provisioner" container. It will be located in the pod that is created to provision your new cluster, in the namespace that corresponds to the Kommander workspace you are trying to create the cluster in.
To find the namespace of your Kommander workspace, click the "Workspaces" tab on the sidebar menu in the Kommander UI. In this example, the Kubernetes namespace of Kommander's Default Workspace is "default-workspace-7ptsl".
Using kubectl, you can list the pods in this namespace to find the pod that corresponds to the new cluster you're trying to create. Substitute the namespace ID you got from the UI in the previous step:
One of the pod names will correspond to the name of the cluster you're trying to create. For example, I was trying to create "my-cluster" so there is a pod in this namespace called "my-cluster-p6ueg".
I can check the logs for the konvoy-provisioner pod in this example with:
This will retrieve the logs from the "konvoy-provisioner" container in the "my-cluster-p6ueg" pod in the "default-workspace-7ptsl" namespace. You will need to substitute in your own namespace and pod names based on the previous steps.
Look for a message that resembles the following:
If you see this message, it means that AWS needs you to open the link in a web browser, log in to your AWS account, subscribe to the required AMI, and accept any relevant terms and conditions. Once you follow the instructions on that page, you should be able to try the cluster creation again successfully.
If this does not resolve your issue, please submit a support ticket:
https://support.d2iq.com/s/article/Opening-a-New-Support-Case
In this case, you will want to check the logs of the "konvoy-provisioner" container. It will be located in the pod that is created to provision your new cluster, in the namespace that corresponds to the Kommander workspace you are trying to create the cluster in.
To find the namespace of your Kommander workspace, click the "Workspaces" tab on the sidebar menu in the Kommander UI. In this example, the Kubernetes namespace of Kommander's Default Workspace is "default-workspace-7ptsl".
Using kubectl, you can list the pods in this namespace to find the pod that corresponds to the new cluster you're trying to create. Substitute the namespace ID you got from the UI in the previous step:
kubectl get pods -n default-workspace-7ptsl
One of the pod names will correspond to the name of the cluster you're trying to create. For example, I was trying to create "my-cluster" so there is a pod in this namespace called "my-cluster-p6ueg".
I can check the logs for the konvoy-provisioner pod in this example with:
kubectl logs -n default-workspace-7ptsl my-cluster-p6ueg konvoy-provisioner
This will retrieve the logs from the "konvoy-provisioner" container in the "my-cluster-p6ueg" pod in the "default-workspace-7ptsl" namespace. You will need to substitute in your own namespace and pod names based on the previous steps.
Look for a message that resembles the following:
Error: Error launching source instance: OptInRequired: In order to use this AWS Marketplace product you need to accept terms and subscribe. To do so please visit https://aws.amazon.com/marketplace/pp?sku=xxxxxxxxx
If you see this message, it means that AWS needs you to open the link in a web browser, log in to your AWS account, subscribe to the required AMI, and accept any relevant terms and conditions. Once you follow the instructions on that page, you should be able to try the cluster creation again successfully.
If this does not resolve your issue, please submit a support ticket:
https://support.d2iq.com/s/article/Opening-a-New-Support-Case