Do you support arm64 architecture machines?
No. DeepSource Enterprise does not support arm64 machines yet.Patching with Kustomize
If you would like to make modifications to Enterprise Server’s K8s manifests, you can patch them with Kustomize. For example, you can customize the number of replicas that you want to use in your environment or specify what node selectors to use for deployment. Please refer to this resource.Can I use a top level load balancer for routing requests to the deployment?
Yes, you can.How do I re-sync the license?
You can check if there are any changes to your license (change of expiry, configuration change, etc) through the License tab on the Replicated admin console. 1. Sync License- Navigate to the “License” tab on the Admin Console
- Click on “Sync License” to get the latest version of the license

- A “License synced successfully” note will appear when the changes are successfully applied.

- Navigate to the “Version History” tab on the Admin Console
- A new release saying “License Change” will now be available
- Click on the “Deploy” button.

Image pulls are failing with imagePullBack error
This most likely happens if your license has expired. Check the status of your license from the admin console. If you still face the error, reach out to the Enterprise Support for help.The spinner is stuck in loop when the first analysis is performed
It is highly likely that the node selector labels haven’t been set, and thus the analysis pods haven’t been scheduled onto the nodes. To investigate this run:<pod-name>
can be fetched by running:
Repositories are not visible when attempting to sync
This can be attributed to misconfiguration in the admin console. To fix this, recreate a new GitHub app private key and upload the same to the admin console, and then redeploy.Unable to view logs for some of the pods
This clearly indicates a firewall issue between the nodes (or VMs), as the CNI (Container Networking Interface) requires the pods to be resolvable with each other over the overlay network across all the nodes. When a firewall is blocking the network, pods from one node, or for that matter, the Kubernetes master node, isn’t able to communicate with the pods on the other node. To resolve this, please refer to this resource.All the pods are pending for more than a minute when running kubectl get pods
You will need to add the node selector labels which you had entered in the admin console onto the nodes. Please refer to this resource.
Support bundle generation has been stuck at X% for the last few hours
If support bundle generation is stuck (or) taking a long time, it is most likely because you’re on older version of KOTS. Please upgrade KOTS using the following command:- Run this command to find support bundle secrets:
- Delete the secrets starting with
supportbundle-*
one-by-one:
- Once done, go to the Admin Console and click on “Generate a support bundle” again.