[BUG] Pod is not re-created although deployment replicas = 1

[lanphan]

What did you do

Follows instruction here to setup kyma on k3d: https://github.com/kyma-incubator/local-kyma
It works ok.

Next, follows "Getting started" document from Kyma here: https://kyma-project.io/docs/1.21/root/getting-started/ till step 5 below

After pod is deleted, I have waited for a long time (more than half an hour) but still don't see new pod is re-created.

Below is script Deployment I use:
https://raw.githubusercontent.com/kyma-project/examples/master/orders-service/deployment/orders-service-deployment.yaml

Which OS & Architecture

• Linux, Windows, MacOS / amd64, x86, ...?

MacOS version 10.15.7 (Intel)

Which version of k3d

• output of k3d version

k3d version v4.4.2
k3s version latest (default)

Which version of docker

• output of docker version and docker info

lanphan@Lans-MacBook-Pro onex-backend % docker version
Client: Docker Engine - Community
Cloud integration: 1.0.12
Version: 20.10.5
API version: 1.41
Go version: go1.13.15
Git commit: 55c4c88
Built: Tue Mar 2 20:13:00 2021
OS/Arch: darwin/amd64
Context: default
Experimental: true

Server: Docker Engine - Community
Engine:
Version: 20.10.5
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: 363e9a8
Built: Tue Mar 2 20:15:47 2021
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.4.4
GitCommit: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
runc:
Version: 1.0.0-rc93
GitCommit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
docker-init:
Version: 0.19.0
GitCommit: de40ad0

lanphan@Lans-MacBook-Pro onex-backend % docker info
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
scan: Docker Scan (Docker Inc., v0.6.0)

Server:
Containers: 12
Running: 2
Paused: 0
Stopped: 10
Images: 37
Server Version: 20.10.5
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 5.10.25-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 5
Total Memory: 8.01GiB
Name: docker-desktop
ID: VFGO:EJYX:Y2MW:HZL7:FFXQ:U7P5:SOIY:FG2R:NU2V:MTKW:ADZM:URNP
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

[iwilltry42]

UPDATE: solved itself

Hi @lanphan 👋
I doubt that this is actually a bug in k3d, as k3d doesn't handle anything related to pods. So it would rather be an issue with k3s run by k3d 😬
However, I can try to help you debug this.. Can you please paste the output of kubectl get pods and kubectl describe deployment <name> in the correct namespace and with the replaced name of the deployment here?
Additionally, it would be good to have the output of docker logs k3d-kyma-server-0 (I think that's what the cluster is called)?

[lanphan]

Hi @iwilltry42 ,

Thanks for your support. Relating to logs you requested, do you need logs BEFORE or AFTER pod deleted?

[iwilltry42]

For everything mentioned, getting the output AFTER the pod was deleted should be enough.

[lanphan]

Hi @iwilltry42 ,

I did retry 3 times, but now everything works fine.
Really don't know why it works now but it didn't work in the past ...

Thanks so much for your kind support. I think we can close this