Genesys Engage on-premises

 View Only

Discussion Thread View

  • 1.  Issue During initiate kubeadm

    Posted 01-19-2023 01:46
    Dear Team,

    I found the below error when I initiated the kubeadm.

    Secondly, my docker is running state and I have never configured the slave node right now, I am only working master node.

    Command:
    " 
    kubeadm init --pod-network-cidr=10.244.0.0/16
    "
    [root@master-node ~]# kubeadm init --pod-network-cidr=10.244.0.0/16
    [init] Using Kubernetes version: v1.26.1
    [preflight] Running pre-flight checks
    [WARNING Hostname]: hostname "master-node" could not be reached
    [WARNING Hostname]: hostname "master-node": lookup master-node on 1.1.1.1:53: no such host
    error execution phase preflight: [preflight] Some fatal errors occurred:
    [ERROR CRI]: container runtime is not running: output: time="2023-01-19T11:45:16+05:00" level=fatal msg="unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
    , error: exit status 1
    [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
    To see the stack trace of this error execute with --v=5 or higher


    [root@master-node ~]# kubectl get nodes
    W0119 11:45:29.494783 18376 loader.go:222] Config not found: /etc/kubernetes/admin.conf
    E0119 11:45:29.497282 18376 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
    E0119 11:45:29.497927 18376 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
    E0119 11:45:29.499606 18376 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
    E0119 11:45:29.501525 18376 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
    E0119 11:45:29.502317 18376 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
    The connection to the server localhost:8080 was refused - did you specify the right host or port?

    "
    #Implementation

    ------------------------------
    Arsalan Nafees
    Individual Only Contact Account
    ------------------------------


  • 2.  RE: Issue During initiate kubeadm

    Posted 01-20-2023 02:33
    Is there any answer to my query?

    ------------------------------
    Arsalan Nafees
    Individual Only Contact Account
    ------------------------------

    Original Message


  • 3.  RE: Issue During initiate kubeadm

    Posted 01-20-2023 04:11
    Hi Arsalan,

    If the above deployment is for GCXI then you should follow the below pages that will be helpful for the deployment

    Genesys CX Insights 9.x Deployment Guide
    Prerequisites: Before you begin installation (genesys.com)
    Installing Kubernetes and Docker in online scenarios (genesys.com)
    Installing Kubernetes and Docker in offline scenarios (genesys.com)

    From the given logs we can see the below issues


    1. There is no host address defined during the kubeadm init, so use something as below (where 192.168.1.45 should be replaced with your master node host address)

    kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.1.45 --kubernetes-version=v1.23.15


    2. This version of Kubernetes in logs (Using Kubernetes version: v1.26.1) is not mentioned as supported/tested in documentation, follow the below

    OS - RHEL/CENTOS 7/8
    Kubernetes - 1.23.15
    Docker - 19.03.15

    3. container runtime is not running with below error

    [ERROR CRI]: container runtime is not running: output: time="2023-01-19T11:45:16+05:00" level=fatal msg="unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""


    This might be due to the incorrect host address or unsupported version docker / Kubernetes starting 1.24 ( dosckershim depreciation)

    Also You have to configure valid host entries in /etc/hosts, add valid firewall rules ( or disable firewalld), disable/permissive selinux, valid DNS resolution, supported version of Docker & Kubernetes



    ------------------------------
    Karthik Eswaran
    ------------------------------

    Original Message


  • 4.  RE: Issue During initiate kubeadm

    Posted 01-23-2023 12:16
    Edited by Evgenii Dremin 01-23-2023 12:16

    I faced another issue at the same step with Kubernetes version: v1.26.1:

    =================
    [ERROR CRI]: container runtime is not running: output: time="2023-01-23T18:12:07+01:00" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
    , error: exit status 1
    =================

    Docker version is 20.10.22
    Linux 7.9 (rhel)

    It's interesting that downgrade to 1.22 solves the issue. 
    Is anyone faced it already? 



    ------------------------------
    Evgenii Dremin
    Deutsche Telekom Business Solutions GmbH
    ------------------------------

    Original Message


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources