Here are some common reasons why your environment could fail to deploy with Humanitec using the Humanitec-managed cluster.
Kubernetes Connection Error
The Kubernetes connection error may occur if Humanitec fails to connect to the Kubernetes API, or if the connection succeeds but Kubernetes fails to execute the deployment request.
Try clicking the deployment button again.
If the error persists, then please send a help request.
When Kubernetes begins to create pods for your workloads, the pod could break due to an improper configuration in the workload's Dockerfile or its configurations.
Check to see if your workload's Dockerfile runs properly. You can see this in the Humanitec interface by going to your app, clicking on the workload, and going to its Logs section.
Failure to Connect to an External Resource
If your app depends on a resource not deployed with Humanitec, such as an external database or API, and Humanitec cannot connect to it, then the deployment will fail.
We recommend enabling logging in your app. You can view these logs in the Humanitec interface by going to your app, clicking on the workload, and then going to its Logs section.
Cannot Access Workload at its configured DNS
Is Ingress configured?
In order for a workload to be accessible via a DNS name, Ingress needs to be configured. You can check to see if Ingress is configured by opening the Workload details screen of the Active Deployment. The Ingress, if configured, should be below Resource dependencies in the left hand column. The DNS name should be shown on the card.
Ingress, if configured, should be below Resource dependencies in the left hand column.
This is most often caused by incorrect Ingress configuration. Ensure that the port Ingress is configured to on the workload is being listened to by one of the services in a container in that workload.
Is the certificate not valid?
If the request has a certificate error, there can be a number of causes:
"Kubernetes Ingress Controller Fake Certificate" is being served
This case is most commonly caused by a conflict between the default ingress controller and the user installed one. If you have set up your own ingress resource definition, ensure that the class field is correctly provided. An example of setting the class field for ingress-nginx is here:
Replace HUMANITEC_TOKEN, HUMANITEC_ORG and DEFINITION_ID with appropriate values.
Features are not available in the UI
If you are not able to see certain features in the Humanitec UI that might be because an ad blocker or other browser setting is interfering with some features on the platform. The reason for this is that Humanitec uses a system called Optimizely for UI feature flags. If you have ad blocking services enabled that block calls to https://cdn.optimizely.com, Optimizely has to be manually removed from the blacklist in your ad-blocking extension or the ad block service has to be disabled in order for you to access all Humanitec features available to you.
Google login is not working
The login to Humanitec via the Google social authentication feature requires 3rd party cookies to be set. More information on this is available on developers.google.com
In general the login via Google needs the permission for 3rd party cookies to be set. This can be blocked by security settings in your browser or by browser add-ons like Privacy Badger. Please enable 3rd party cookies to set when using the Google sign-in to Humanitec.