Go Report | Travis | CircleCI | Azure Test | Azure Release | License |
---|---|---|---|---|---|
oneinfra
is a Kubernetes as a Service platform. It empowers you to
provide or consume Kubernetes clusters at scale, on any platform or
service provider. You decide.
You can read more about its design here.
Kubernetes version | Deployable with | Default in | ||
---|---|---|---|---|
1.15.11 |
20.04.0-alpha6 |
|||
1.16.9 |
20.04.0-alpha6 |
|||
1.17.5 |
20.04.0-alpha6 |
|||
1.18.2 |
20.04.0-alpha6 |
20.04.0-alpha6 |
||
1.19.0-alpha.1 |
20.04.0-alpha6 |
Build has been tested with go versions 1.13 and 1.14.
$ GO111MODULE=on go get github.com/oneinfra/oneinfra/...@20.04.0-alpha6
This should have installed the following binaries:
-
oi-local-hypervisor-set
: allows you to testoneinfra
locally in your machine, creating hypervisors as Docker containers. This is whereoneinfra
will schedule control plane components. -
oi
: CLI tool that allows you to testoneinfra
locally in a standalone way, without requiring Kubernetes to store manifests. -
oi-manager
: Kubernetes set of controllers that reconcile defined clusters.
For the quick start you can either leverage Kubernetes as a management cluster, or you can go with the standalone approach if you don't want to use Kubernetes.
- Requirements
- Docker
If you don't want to deploy Kubernetes to test oneinfra
, you can use
the oi
CLI tool that will allow you to test the reconciliation
processes of oneinfra
without the need of a Kubernetes cluster.
$ oi-local-hypervisor-set create | oi cluster inject | oi reconcile > cluster-manifests.conf
And access it:
$ cat cluster-manifests.conf | oi cluster admin-kubeconfig > cluster-kubeconfig.conf
$ kubectl --kubeconfig=cluster-kubeconfig.conf cluster-info
Kubernetes master is running at https://172.17.0.4:30000
In this mode it's very important to understand that oi
will read
manifests from stdin
and output them into stdout
, make sure you
keep a file up to date with the latest reconciled resources -- this is
why this model is not suitable for production.
- Requirements
- A Kubernetes cluster that will be the management cluster
- The management cluster needs to reach the hypervisors you create
- Docker, for creating fake local hypervisors
-
Install
kind
. If you already have a Kubernetes cluster you can use, you can skip this step.$ kind create cluster
-
Deploy
cert-manager
andoneinfra
.$ kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v0.14.1/cert-manager.yaml $ kubectl wait --for=condition=Available deployment --timeout=2m -n cert-manager --all $ kubectl apply -f https://raw.githubusercontent.com/oneinfra/oneinfra/20.04.0-alpha6/config/generated/all.yaml $ kubectl wait --for=condition=Available deployment --timeout=2m -n oneinfra-system --all
-
Create a local set of fake hypervisors, so
oneinfra
can schedule cluster control plane components somewhere. You can also define your own set of hypervisors if you prefer.$ oi-local-hypervisor-set create --tcp | kubectl apply -f -
In this case, we need to use the
--tcp
flag, so theoneinfra
controller manager can talk to the CRI endpoints of the fake hypervisors.Hadn't we provided the
--tcp
flag here, we would have needed to mount the UNIX sockets of the different hypervisors inside the controller manager, leading to an even more artificial setup.In production environments, it is a user responsibility to manage the
Hypervisor
resources with remote CRI endpoints. -
Now, create a managed cluster:
$ kubectl apply -f https://raw.githubusercontent.com/oneinfra/oneinfra/20.04.0-alpha6/config/samples/simple-cluster.yaml $ kubectl wait --for=condition=ReconcileSucceeded --timeout=2m cluster simple-cluster
-
And access it:
$ kubectl get cluster simple-cluster -o yaml | oi cluster admin-kubeconfig > simple-cluster-kubeconfig.conf $ kubectl --kubeconfig=simple-cluster-kubeconfig.conf cluster-info Kubernetes master is running at https://172.17.0.5:30000
-
(optional) You can then create a second managed cluster, this one comprised by three control plane instances:
$ kubectl apply -f https://raw.githubusercontent.com/oneinfra/oneinfra/20.04.0-alpha6/config/samples/ha-cluster.yaml $ kubectl wait --for=condition=ReconcileSucceeded --timeout=2m cluster ha-cluster
-
And access it:
$ kubectl get cluster ha-cluster -o yaml | oi cluster admin-kubeconfig > ha-cluster-kubeconfig.conf $ kubectl --kubeconfig=ha-cluster-kubeconfig.conf cluster-info Kubernetes master is running at https://172.17.0.5:30002
-
-
List clusters and components on the management cluster:
$ kubectl get clusters -A NAMESPACE NAME KUBERNETES VERSION API SERVER ENDPOINT VPN VPN CIDR AGE default ha-cluster 1.18.2 https://172.17.0.5:30001 false 62s default simple-cluster 1.18.2 https://172.17.0.5:30000 false 2m7s
$ kubectl get components -A NAMESPACE NAME CLUSTER ROLE HYPERVISOR AGE default ha-cluster-control-plane-hvz2h ha-cluster control-plane test-private-hypervisor-0 65s default ha-cluster-control-plane-ingress-8scc5 ha-cluster control-plane-ingress test-public-hypervisor-0 65s default ha-cluster-control-plane-j52xp ha-cluster control-plane test-private-hypervisor-0 65s default ha-cluster-control-plane-l4flc ha-cluster control-plane test-private-hypervisor-0 65s default simple-cluster-control-plane-bcx9g simple-cluster control-plane test-private-hypervisor-0 2m10s default simple-cluster-control-plane-ingress-5sdfh simple-cluster control-plane-ingress test-public-hypervisor-0 2m10s
Then play as much as you want by creating new clusters, deleting existing ones, or anything you want to try. Have fun!
You can have a more detailed read at the documentation on how to
define clusters once you have set up oneinfra
.
You can read more details about the worker joining process here.
oneinfra
is licensed under the terms of the Apache 2.0 license.
Copyright (C) 2020 Rafael Fernández López <ereslibre@ereslibre.es>
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.