Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 6 views

    新文字文件

    Uploaded by

    hiroqqwwee

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd

    新文字文件

    Uploaded by

    hiroqqwwee
    6 views2 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    6 views2 pages

    新文字文件

    Uploaded by

    hiroqqwwee

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    You are on page 1of 2

    root@hiro-k8-master:~# sudo kubeadm init --pod-network-cidr=10.244.0.

    0/16
    I1009 13:29:23.145212 22561 version.go:256] remote version is much newer:
    v1.31.0; falling back to: stable-1.28
    [init] Using Kubernetes version: v1.28.14
    [preflight] Running pre-flight checks
    [WARNING FileExisting-socat]: socat not found in system path
    [preflight] Pulling images required for setting up a Kubernetes cluster
    [preflight] This might take a minute or two, depending on the speed of your
    internet connection
    [preflight] You can also perform this action in beforehand using 'kubeadm config
    images pull'
    W1009 13:29:40.514464 22561 checks.go:835] detected that the sandbox image
    "registry.k8s.io/pause:3.8" of the container runtime is inconsistent with that used
    by kubeadm. It is recommended that using "registry.k8s.io/pause:3.9" as the CRI
    sandbox image.
    [certs] Using certificateDir folder "/etc/kubernetes/pki"
    [certs] Generating "ca" certificate and key
    [certs] Generating "apiserver" certificate and key
    [certs] apiserver serving cert is signed for DNS names [hiro-k8-master kubernetes
    kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and
    IPs [10.96.0.1 10.52.52.111]
    [certs] Generating "apiserver-kubelet-client" certificate and key
    [certs] Generating "front-proxy-ca" certificate and key
    [certs] Generating "front-proxy-client" certificate and key
    [certs] Generating "etcd/ca" certificate and key
    [certs] Generating "etcd/server" certificate and key
    [certs] etcd/server serving cert is signed for DNS names [hiro-k8-master localhost]
    and IPs [10.52.52.111 127.0.0.1 ::1]
    [certs] Generating "etcd/peer" certificate and key
    [certs] etcd/peer serving cert is signed for DNS names [hiro-k8-master localhost]
    and IPs [10.52.52.111 127.0.0.1 ::1]
    [certs] Generating "etcd/healthcheck-client" certificate and key
    [certs] Generating "apiserver-etcd-client" certificate and key
    [certs] Generating "sa" key and public key
    [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
    [kubeconfig] Writing "admin.conf" kubeconfig file
    [kubeconfig] Writing "kubelet.conf" kubeconfig file
    [kubeconfig] Writing "controller-manager.conf" kubeconfig file
    [kubeconfig] Writing "scheduler.conf" kubeconfig file
    [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
    [control-plane] Using manifest folder "/etc/kubernetes/manifests"
    [control-plane] Creating static Pod manifest for "kube-apiserver"
    [control-plane] Creating static Pod manifest for "kube-controller-manager"
    [control-plane] Creating static Pod manifest for "kube-scheduler"
    [kubelet-start] Writing kubelet environment file with flags to file
    "/var/lib/kubelet/kubeadm-flags.env"
    [kubelet-start] Writing kubelet configuration to file
    "/var/lib/kubelet/config.yaml"
    [kubelet-start] Starting the kubelet
    [wait-control-plane] Waiting for the kubelet to boot up the control plane as static
    Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
    [apiclient] All control plane components are healthy after 7.002747 seconds
    [upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the
    "kube-system" Namespace
    [kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the
    configuration for the kubelets in the cluster
    [upload-certs] Skipping phase. Please see --upload-certs
    [mark-control-plane] Marking the node hiro-k8-master as control-plane by adding the
    labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-
    external-load-balancers]
    [mark-control-plane] Marking the node hiro-k8-master as control-plane by adding the
    taints [node-role.kubernetes.io/control-plane:NoSchedule]
    [bootstrap-token] Using token: 1e6c87.y7iul2m6zxtr0kmo
    [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
    [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
    [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs
    in order for nodes to get long term certificate credentials
    [bootstrap-token] Configured RBAC rules to allow the csrapprover controller
    automatically approve CSRs from a Node Bootstrap Token
    [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node
    client certificates in the cluster
    [bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public"
    namespace
    [kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable
    kubelet client certificate and key
    [addons] Applied essential addon: CoreDNS
    [addons] Applied essential addon: kube-proxy

    Your Kubernetes control-plane has initialized successfully!

    To start using your cluster, you need to run the following as a regular user:

    mkdir -p $HOME/.kube
    sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
    sudo chown $(id -u):$(id -g) $HOME/.kube/config

    Alternatively, if you are the root user, you can run:

    export KUBECONFIG=/etc/kubernetes/admin.conf

    You should now deploy a pod network to the cluster.


    Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
    https://kubernetes.io/docs/concepts/cluster-administration/addons/

    Then you can join any number of worker nodes by running the following on each as
    root:

    kubeadm join 10.52.52.111:6443 --token 1e6c87.y7iul2m6zxtr0kmo \


    --discovery-token-ca-cert-hash
    sha256:34755291755ea0a09263192d38ae52226371cbe13dcebc7826246676ac71a939

    You might also like