4.1 KiB

Raw Permalink Blame History

How to Debug Your Kruise Rollout

Way 1: Debug your kruise Rollout with Pod (Recommended)

First Step: Start your kubernetes cluster

Requirements:

Linux system, MacOS, or Windows Subsystem for Linux 2.0 (WSL 2)
Docker installed (follow the official docker installation guide to install if need be)
Kubernetes cluster >= v1.19.0
Kubectl installed and configured

Kruise Rollout relies on Kubernetes as control plane. The control plane could be any managed Kubernetes offering or your own cluster.

For local deployment and test, you could use kind or minikube. For production usage, you could use Kubernetes services provided by cloud providers.

Option 1: Start your kubernetes cluster with kind (Recommended)

Follow this guide to install kind.

Then spins up a kind cluster:

cat <<EOF | kind create cluster --image=kindest/node:v1.22.15 --config=-
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: worker
- role: worker
- role: worker
EOF

Option 2: Start your kubernetes cluster with minikube

Follow the minikube installation guide.

Then spins up a MiniKube cluster:

minikube start

Second Step (Optional): Install Kruise

If you want to use Workload such as CloneSet, Advanced StatefulSet and Advanced DaemonSet, you have to install Kruise:

# Firstly add openkruise charts repository if you haven't do this.
$ helm repo add openkruise https://openkruise.github.io/charts/

# [Optional]
$ helm repo update

# Install the latest version.
$ helm install kruise openkruise/kruise --version 1.3.0

Third Step: Deploy your kruise Rollout with a deployment

1. Generate code and manifests in your branch

Make your own code changes and validate the build by running make build in rollouts directory.

2. Deploy customized controller manager

The deployment can be done by following steps.

Prerequisites: prepare an image registry, it can be docker hub or your private hub.
step 1: export IMG=<image_name> to specify the target image name. e.g., export IMG=$DOCKERID/kruise-rollout:test;
step 2: make docker-build to build the image locally and make docker-push to push the image to registry;
step 3: export KUBECONFIG=<your_k8s_config> to specify the k8s cluster config. e.g., export KUBECONFIG=$~/.kube/config;
step 4:
- 4.1: make deploy to deploy Rollout to the k8s cluster with the IMG you have packaged, if the cluster has not installed Rollout or has installed via make deploy;
- 4.2: if the cluster has installed Rollout via helm chart, we suggest you just update your IMG into it with kubectl set image -n kruise-rollout deployment kruise-rollout-controller-manager manager=${IMG};

Tips:

You have to run ./scripts/uninstall.sh to uninstall Rollout if you installed it using make deploy.

3.View logs of your Rollout

You can perform manual tests and use kubectl logs -n kruise-rollout <kruise-rollout-pod-name> to check controller logs for debugging, and you can see your <kruise-rollout-pod-name> by applying kubectl get pod -n kruise-rollout.

Way 2: Debug your Rollout locally (NOT Recommended)

Kubebuilder default make run does not work for webhooks since its scaffolding code starts webhook server using kubernetes service and the service usually does not work in local dev environment.

We workarounds this problem by allowing to start webbook server in local host directly. With this fix, one can start/debug Rollout process locally which connects to a local or remote Kubernetes cluster. Several extra steps are needed to make it work:

Setup host and run your Rollout

First, make sure your kubernetes cluster is running.

Second, make sure kube-apiserver could connect to your local machine.

Then, run rollout locally with WEBHOOK_HOST env:

export KUBECONFIG=${PATH_TO_CONFIG}
export WEBHOOK_HOST=${YOUR_LOCAL_IP}

make install
make run

4.1 KiB Raw Permalink Blame History