kubeadm started cluster on localhost.

607 views
Skip to first unread message

Abdelfattah Mahran

unread,
Dec 30, 2016, 2:20:14 PM12/30/16
to Kubernetes user discussion and Q&A
hi all,

I'm using kubeadm and it started the cluster on localhost. how can I access this cluster from outside. I gave kubeadm the needed parameters.

I'm using Centos-7

kubeadm init --skip-preflight-checks --api-advertise-addresses=10.103.12.23 --pod-network-cidr=10.244.0.0/16 --use-kubernetes-version=1.4.7


[root@centos-master ~]# kubectl cluster-info
Kubernetes master is running at http://localhost:8080

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
[root@centos-master ~]# curl http://localhost:8080
{
  "paths": [
    "/api",
    "/api/v1",
    "/apis",
    "/apis/apps",
    "/apis/apps/v1alpha1",
    "/apis/authentication.k8s.io",
    "/apis/authorization.k8s.io",
    "/apis/autoscaling",
    "/apis/autoscaling/v1",
    "/apis/batch",
    "/apis/batch/v1",
    "/apis/batch/v2alpha1",
    "/apis/certificates.k8s.io",
    "/apis/extensions",
    "/apis/extensions/v1beta1",
    "/apis/policy",
    "/apis/policy/v1alpha1",
    "/apis/storage.k8s.io",
    "/apis/storage.k8s.io/v1beta1",
    "/healthz",
    "/healthz/ping",
    "/logs",
    "/metrics",
    "/swaggerapi/",
    "/ui/",
    "/version"
  ]
}[root@centos-master ~]# kubectl config view
apiVersion: v1
clusters: []
contexts: []
current-context: ""
kind: Config
preferences: {}
users: []


also I had to use --skip-preflight-checks because it gave me the below error if anyone has a clue it would be great.


preflight] The system verification failed. Printing the output from the verification:
OS: Linux
KERNEL_VERSION: 3.10.0-514.el7.x86_64
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
DOCKER_VERSION: 1.10.3
DOCKER_GRAPH_DRIVER: devicemapper
[preflight] Some fatal errors occurred:
        failed to parse kernel config: unable to load kernel module "configs": output - "modprobe: FATAL: Module configs not found.\n", err - exit status 1
[preflight] If you know what you are doing, you can skip pre-flight checks with `--skip-preflight-checks`

[root@centos-master ~]# uname -a
Linux centos-master 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[root@centos-master ~]# lsb_release -a
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.3.1611 (Core)
Release:        7.3.1611
Codename:       Core
[root@centos-master ~]#

Thanks,
best regards,
Reply all
Reply to author
Forward
0 new messages