Verify Webhook Configuration

Oct 13, 2025 by talynt.org 18 views

BUG: Kruise Pod Based on Helm Deployment Cannot Be Created

Kruise is a Kubernetes-based project that provides a set of tools for managing and automating the deployment of applications. It is designed to be highly scalable and flexible, making it an ideal choice for large-scale deployments. However, in some cases, users may encounter issues when deploying Kruise using Helm. In this article, we will discuss a bug that prevents the creation of a Kruise pod based on a Helm deployment.

When installing Kruise 1.5.0 using Rancher, users may encounter an error that prevents the creation of a Kruise pod. The error message is typically displayed in the ReplicaSet, and it may look something like this:

  Warning  FailedCreate  4m49s (x19 over 26m)  replicaset-controller  Error creating: Internal error occurred: failed calling webhook "mpod.kb.io": Post https://kruise-webhook-service.kruise-system.svc:443/mutate-pod?timeout=10s: dial tcp xx.xx.xxx.xxx:443: connect: connection refused

This error message is unusual because it occurs before the pod is even created. It appears that there is a sequence error in the deployment process.

When deploying Kruise using Helm, users expect the related resources to be created normally. This includes the creation of the Kruise pod, which is a critical component of the deployment process.

To reproduce the issue, follow these steps:

Install Kruise 1.5.0 using Rancher.
Verify that the ReplicaSet displays the error message mentioned earlier.
Check the deployment logs to see if there are any other error messages.

To help resolve this issue, please provide the following information:

Kruise version: 1.5.0
Kubernetes version (use kubectl version): v1.18.20
Install details (e.g. helm install args): using args: featureGates: "ImagePullJobGate=true,KruiseDaemon=false"
Others: (please provide any additional information that may be relevant to the issue)

The following environment details are relevant to this issue:

Kruise Version: 1.5.0
Kubernetes Version: v1.18.20
Install Details: using args: featureGates: "ImagePullJobGate=true,KruiseDaemon=false"

Based on the error message, it appears that there is a sequence error in the deployment process. This may be caused by a number of factors, including:

Webhook Failure: The webhook "mpod.kb.io" may be failing to create the pod, resulting in the sequence error.
Deployment Configuration: The deployment configuration may be incorrect, leading to the sequence error.
Kubernetes Version: The Kubernetes version may be causing the issue, particularly if it is an older version.

To troubleshoot this issue, follow these steps:

Verify Webhook Configuration: Verify that the webhook "mpod.kb.io" is correctly configured and functioning as expected.
Check Deployment Configuration: Check the deployment configuration to ensure that it is correct and not causing the sequence error.
Update Kubernetes Version: If the issue is caused by an older Kubernetes version, update to a newer version to see if the issue is resolved.
Enable Debug Logging: Enable debug logging to see if there are any other error messages that may be relevant to the issue.

In conclusion, the bug that prevents the creation of a Kruise pod based on a Helm deployment is a complex issue that requires careful troubleshooting. By following the steps outlined in this article, users should be able to identify and resolve the issue. If the issue persists, please provide additional information and logs to help resolve the issue.
Q&A: Kruise Pod Based on Helm Deployment Cannot Be Created

In our previous article, we discussed a bug that prevents the creation of a Kruise pod based on a Helm deployment. In this article, we will provide a Q&A section to help users better understand the issue and how to resolve it.

A: The error message "Error creating: Internal error occurred: failed calling webhook "mpod.kb.io"" is typically caused by a sequence error in the deployment process. This may be due to a number of factors, including webhook failure, deployment configuration issues, or Kubernetes version issues.

A: To verify the webhook configuration, follow these steps:

Check the webhook configuration file to ensure that it is correctly configured and functioning as expected.
Verify that the webhook service is running and accessible.
Check the deployment logs to see if there are any error messages related to the webhook.

A: The possible causes of the sequence error include:

Webhook failure: The webhook "mpod.kb.io" may be failing to create the pod, resulting in the sequence error.
Deployment configuration: The deployment configuration may be incorrect, leading to the sequence error.
Kubernetes version: The Kubernetes version may be causing the issue, particularly if it is an older version.

A: To troubleshoot the issue, follow these steps:

Verify the webhook configuration.
Check the deployment configuration.
Update the Kubernetes version if necessary.
Enable debug logging to see if there are any other error messages that may be relevant to the issue.

A: The troubleshooting steps for each possible cause are as follows:

Webhook Failure:
- Verify that the webhook service is running and accessible.
- Check the deployment logs to see if there are any error messages related to the webhook.
- Update the webhook configuration if necessary.
Deployment Configuration:
- Check the deployment configuration file to ensure that it is correctly configured and functioning as expected.
- Verify that the deployment configuration is not causing the sequence error.
- Update the deployment configuration if necessary.
Kubernetes Version:
- Check the Kubernetes version to ensure that it is up-to-date.
- Update the Kubernetes version if necessary.
- Verify that the issue is resolved after updating the Kubernetes version.

A: To enable debug logging, follow these steps:

Add the following flag to the deployment configuration file: --v=5
Restart the deployment to apply the changes.
Check the deployment logs to see if there are any debug messages that may be relevant to the issue.

In conclusion, the Q&A section provides additional information and troubleshooting steps to help users resolve the issue of a Kruise pod based on a Helm deployment cannot be created. By following the steps outlined in this article, users should be able to identify and resolve the issue. If the issue persists, please provide additional information and logs to help resolve the issue.