The troubleshooting section aims to identify the most common recurring problems the users face when they install and start using Kyma, as well as the most suitable solutions to these problems.

If you can't find a solution, don't hesitate to create a GitHub issue or reach out to our Slack channel to get direct support from the community.

See the full list of Kyma troubleshooting guides:

General troubleshooting guides

• Component doesn't work after successful installation
• Local Kyma deployment fails with pending Pods
• Provisioning k3d fails on a Linux machine
• Error for kubectl port forwarding
• Kyma domain is not resolvable
• Kyma resource is misconfigured
• Cannot create a volume snapshot

API Exposure

• Cannot connect to a service exposed by an APIRule
  • Basic diagnostics
  • 401 Unauthorized or 403 Forbidden
  • 404 Not Found
  • 500 Internal Server Error
• External DNS management
  • Connection refused or timeout
  • Could not resolve host
  • Resource ignored by the controller
• Certificate management - Issuer not created
• Kyma Gateway - not reachable
• Pods stuck in Pending/Failed/Unknown state after an upgrade
• Issues when creating an APIRule - various reasons

Eventing

• Kyma Eventing - Basic Diagnostics
• NATS JetStream backend troubleshooting
• Subscriber receives irrelevant events
• Eventing backend stopped receiving events due to full storage
• Published events are pending in the stream

Observability

• Prometheus Istio Server restarting or in crashback loop
• Component doesn't work after successful installation

Security

• Issues with certificates on Gardener

Serverless

• Failure to build Functions
• Failing Function container
• Function debugger stops at dependency files
• Functions failing to build on k3d
• Serverless periodically restarting

Service Mesh

• Can't access a Kyma endpoint (503 status code)
• Connection refused errors
• Issues with Istio sidecar injection
• Incompatible Istio sidecar version after Kyma upgrade