coreos-kubernetes | CoreOS Container Linux+Kubernetes documentation | Continuous Deployment library

by coreos Shell Version: v0.8.6 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(6)Vulnerabilities Install Support

kandi X-RAY | coreos-kubernetes Summary

coreos-kubernetes is a Shell library typically used in Devops, Continuous Deployment, Docker applications. coreos-kubernetes has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This repo is not in alignment with current versions of Kubernetes, and will not be active in the future. The CoreOS Kubernetes documentation has been moved to the tectonic-docs repo, where it will be published and updated. For tested, maintained, and production-ready Kubernetes instructions, see our Tectonic Installer documentation. The Tectonic Installer provides a Terraform-based Kubernetes installation. It is open source, uses upstream Kubernetes and can be easily customized. This repo contains tooling and documentation around deploying Kubernetes using CoreOS Container Linux. Initial setup of a Kubernetes cluster is covered, but ongoing maintenance and updates of the cluster is not addressed. If you're looking for kube-aws, it has been moved to a new dedicated repository. All outstanding AWS-related issues and PRs should be moved to there. This repository will continue to host development on single and multi node vagrant distributions.

Support

Quality

Security

License

Reuse

Support

coreos-kubernetes has a medium active ecosystem.

It has 1107 star(s) with 494 fork(s). There are 83 watchers for this library.

It had no major release in the last 12 months.

There are 119 open issues and 338 have been closed. On average issues are closed in 342 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of coreos-kubernetes is v0.8.6

Quality

coreos-kubernetes has no bugs reported.

Security

coreos-kubernetes has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

coreos-kubernetes is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

coreos-kubernetes releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of coreos-kubernetes

Get all kandi verified functions for this library.

coreos-kubernetes Key Features

No Key Features are available at this moment for coreos-kubernetes.

coreos-kubernetes Examples and Code Snippets

No Code Snippets are available at this moment for coreos-kubernetes.

Community Discussions

Trending Discussions on coreos-kubernetes

Fresh Install Kubernetes worker nodes never become "Ready"

Kubernetes: how to enable API Server Bearer Token Auth?

kube-dns keeps restarting with kubenetes on coreos

calico-node fails starting on worker node

fork/exec /usr/bin/rkt: permission denied

hyperkube doesn't start any manifest from /etc/kubernetes/manifests

QUESTION

Fresh Install Kubernetes worker nodes never become "Ready"

Asked 2017-Jun-12 at 14:51

I've been battling a kubernetes install problem. We started up a new openstack environment and the scripts that work in the old fail environment fail in the new one.

We are using K8s v1.5.4 using these scripts: https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/generic

CoreOS 1298.7.0

The master seems to come up fine. I can deploy pods to it, always shows ready when running kubectl get nodes

The worker installation script runs, however it never shows a ready state.

...

ANSWER

Answered 2017-Apr-21 at 21:45

You need to check if you add your IP address in the SSL generation file (openssl.cnf) for the master. Try to recreate your certificate with the IP of your dns server too ( if you follow coreOS it's 10.3.0.1 ). Your openssl.cnf will look like this:

Source https://stackoverflow.com/questions/43419789

QUESTION

Kubernetes: how to enable API Server Bearer Token Auth?

Asked 2017-Mar-28 at 18:22

I've been trying to enabled token auth for HTTP REST API Server access from a remote client.

I installed my CoreOS/K8S cluster controller using this script: https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/generic/controller-install.sh

My cluster works fine. This is a TLS installation so I need to configure any kubectl clients with the client certs to access the cluster.

I then tried to enable token auth via running:

...

ANSWER

Answered 2017-Mar-28 at 16:50

I think your kube-apiserver dies because it's can't find the /etc/kubernetes/token. That's because on your deployment the apiserver is a static pod therefore running in a container which in turn means it has a different root filesystem than that of the host.

Look into /etc/kubernetes/manifests/kube-apiserver.yaml and add a volume and a volumeMount like this (I have omitted the lines that do not need changing and don't help in locating the correct section):

Source https://stackoverflow.com/questions/43072514

QUESTION

kube-dns keeps restarting with kubenetes on coreos

Asked 2017-Mar-24 at 19:51

I have Kubernetes installed on Container Linux by CoreOS alpha (1353.1.0) using hyperkube v1.5.5_coreos.0 using my fork of coreos-kubernetes install scripts at https://github.com/kfirufk/coreos-kubernetes.

I have two ContainerOS machines.

coreos-2.tux-in.com resolved as 192.168.1.2 as controller
coreos-3.tux-in.com resolved as 192.168.1.3 as worker

kubectl get pods --all-namespaces returns

...

ANSWER

Answered 2017-Mar-13 at 18:06

kube-dns has a readiness probe that tries resolving trough the Service IP of kube-dns. Is it possible that there is a problem with your Service network?

Check out the answer and solution here: kubernetes service IPs not reachable

Source https://stackoverflow.com/questions/42637493

QUESTION

calico-node fails starting on worker node

Asked 2017-Mar-12 at 17:28

I'm trying to install Kubernetes.

configuration details:

Controler

OS: Container Linux by CoreOS alpha (1339.0.0)
LAN IP: 192.168.1.2
FQDN: coreos-2.tux-in.com
environment variables used for installation:
...

ANSWER

Answered 2017-Mar-12 at 17:28

I'd check journalctl -xe on the host where calico-node is failing to start. Since you get nothing from kubectl logs calico-node... it sounds like the containers are failing to even start up.

Source https://stackoverflow.com/questions/42741272

QUESTION

fork/exec /usr/bin/rkt: permission denied

Asked 2017-Mar-11 at 21:57

I'm trying to install Kubernetes.

configuration details:

Controler

OS: Container Linux by CoreOS alpha (1339.0.0)
LAN IP: 192.168.1.2
FQDN: coreos-2.tux-in.com
environment variables used for installation:
...

ANSWER

Answered 2017-Mar-11 at 21:57

it was a simple problem.

I point kubelet.service to run rkt with /opt/bin/host-rkt that contains:

Source https://stackoverflow.com/questions/42740925

QUESTION

hyperkube doesn't start any manifest from /etc/kubernetes/manifests

Asked 2017-Mar-04 at 15:05

I have Container Linux by CoreOS alpha (1325.1.0) Installed on a pc at home.

I played with kubernetes for a couple of month, but now after reinstalling ContainerOS and trying to install kubernetes using my fork at https://github.com/kfirufk/coreos-kubernetes I fail to properly install kubernetes.

I use hyperkube image v1.6.0-beta.0_coreos.0.

the problem is that it seems that hyperkube doesn't try to initiate any manifests from /etc/kubernetes/manifests. I configured kubelet to run with rkt.

when I run journalctl -xef -u kubelet after restarting kubelet, I get the following output:

...

ANSWER

Answered 2017-Mar-04 at 15:05

thanks to @AntoineCotten the problem was easily resolved.

first, I downgraded hyperkube from v1.6.0-beta.0_coreos.0 to v1.5.3_coreos.0. then I noticed an error in the kubelet log that made me understand that I had a major typo in /opt/bin/host-rkt.

I had exec nsenter -m -u -i -n -p -t 1 -- /usr/bin/rkt "\$@" instead of exec nsenter -m -u -i -n -p -t 1 -- /usr/bin/rkt "$@".

I escaped the $ when trying to paste the command line arguments, which then.. didn't. so.. not using 1.6.0-beta0 for now, that's ok! and fixed the script. now everything works again. thanks

Source https://stackoverflow.com/questions/42473930

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install coreos-kubernetes

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: