[Solved]
Finally I was able to find the root cause and fix it.
The subjected error was due to containerD starting on a linux system without enabling SystemdCgroup. That means, CentOS8 at this time of writing won't initialized containerD with SystemdCgroup awareness. To enable it;
edit /etc/containerd/config.toml
and insert a line SystemdCgroup = true after following line
[plugins.\"io.containerd.grpc.v1.cri\".containerd.runtimes.runc.options\]
finally it should looks like
[plugins.\"io.containerd.grpc.v1.cri\".containerd.runtimes.runc.options\]
SystemdCgroup = ture
Note: Indent is required.
WIth this setting applied, you can restart the service systemctl restart containerd and may be reboot the whole Kubernetes cluster.
Once your cluster back in running, you can deploy the ECK without a problem.