Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cilium status reports Kubernetes as disabled with InCluster config #1753

Closed
tgraf opened this issue Oct 14, 2017 · 5 comments
Closed

cilium status reports Kubernetes as disabled with InCluster config #1753

tgraf opened this issue Oct 14, 2017 · 5 comments
Assignees
@aanm
Labels
kind/bug This is a bug in the Cilium logic. need-more-info More information is required to further debug or fix the issue. sig/k8s Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.
Milestone
0.13

Comments

@tgraf
Copy link
Member

tgraf commented Oct 14, 2017 

kubectl -n kube-system exec -ti cilium-07j4c cilium status
KVStore:            Ok         Etcd: http://127.0.0.1:2379 - (Leader) 3.1.5
ContainerRuntime:   Ok
Kubernetes:         Disabled
Cilium:             Ok         OK
NodeMonitor:        Listening for events on 2 CPUs with 64x4096 of shared memory
@tgraf tgraf added the kind/bug This is a bug in the Cilium logic. label Oct 14, 2017
@tgraf tgraf added this to the 0.13 milestone Oct 14, 2017
@borkmann borkmann added the sig/k8s Impacts the kubernetes API, or kubernetes -> cilium internals translation layers. label Oct 16, 2017
@aanm
Copy link
Member

aanm commented Oct 24, 2017

I've tested locally, I can't replicate it

$ kubectl -n kube-system exec -ti cilium-6mgvv cilium status
KVStore:            Ok   Etcd: https://192.168.33.11:2379 - (Leader) 3.2.7
ContainerRuntime:   Ok   
Kubernetes:         Ok   OK
Cilium:             Ok   OK
NodeMonitor:        Listening for events on 2 CPUs with 64x4096 of shared memory

@aanm aanm added the need-more-info More information is required to further debug or fix the issue. label Oct 24, 2017
@tgraf
Copy link
Member Author

tgraf commented Oct 24, 2017

I got into this state by using the old DaemonSet file pre InClusterConfig but with the kubeconfig option removed. The DaemonSet was likely missing the environment variable definitions but still seemed to connect to the API server.

@aanm
Copy link
Member

aanm commented Oct 25, 2017

I'll try this with the new daemon set file without any InClusterConfig to verify its behavior.

@aanm
Copy link
Member

aanm commented Oct 25, 2017

I don't see how this can happen because since the env variables KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_HOST will always be set when using the daemon set:

func IsEnabled() bool {
	return config.APIServer != "" ||
		config.KubeconfigPath != "" ||
		(os.Getenv("KUBERNETES_SERVICE_HOST") != "" &&
			os.Getenv("KUBERNETES_SERVICE_PORT") != "")
}

@tgraf
Copy link
Member Author

tgraf commented Oct 29, 2017

Can no longer reproduce

@tgraf tgraf closed this as completed Oct 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aanm aanm

Labels
kind/bug This is a bug in the Cilium logic. need-more-info More information is required to further debug or fix the issue. sig/k8s Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.
Projects
None yet
Milestone
0.13
Development

No branches or pull requests
3 participants
@borkmann @tgraf @aanm