内容简介:You can
Go Report | Travis | CircleCI | Azure Test | Azure Release | License |
---|---|---|---|---|---|
oneinfra
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 .
Managed Kubernetes versions
Kubernetes version | Deployable with | Default in | ||
---|---|---|---|---|
1.15.11 |
20.04.0-alpha1 |
|||
1.16.8 |
20.04.0-alpha1 |
|||
1.17.4 |
20.04.0-alpha1 |
|||
1.18.0 |
20.04.0-alpha1 |
20.04.0-alpha1 |
||
1.19.0-alpha.1 |
20.04.0-alpha1 |
Go install
Build has been tested with go versions 1.13 and 1.14.
$ GO111MODULE=on go get github.com/oneinfra/oneinfra/...@master
This should have installed the following binaries:
-
oi-local-cluster
: allows you to testoneinfra
locally in your machine, creating Docker containers as hypervisors. -
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.
Quick start
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.
- With Kubernetes as a management cluster
- Without Kubernetes (for testing purposes only)
You can also read documentation on how to define clusters once you have set up oneinfra
.
With Kubernetes as a management cluster
- 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
and oneinfra
.
$ 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/master/config/generated/all.yaml
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-cluster cluster create --remote | kubectl apply -f -
Now, create a managed cluster:
$ kubectl apply -f https://raw.githubusercontent.com/oneinfra/oneinfra/master/config/samples/simple-cluster.yaml $ kubectl wait --for=condition=ReconcileSucceeded --timeout=2m cluster simple-cluster $ kubectl get cluster simple-cluster -o yaml | oi cluster admin-kubeconfig > simple-cluster.conf
And access it:
$ kubectl --kubeconfig=simple-cluster.conf cluster-info Kubernetes master is running at https://172.17.0.5:30000
Without Kubernetes (for testing purposes only)
- Requirements
- Docker
If you don't want to deploy Kubernetes to test oneinfra
, you can try the oi
CLI tool that will allow you to test the reconciliation processes of oneinfra
without the need of a Kubernetes cluster.
$ mkdir ~/.kube $ oi-local-cluster cluster create | \ oi cluster inject --name simple-cluster | \ oi component inject --name controlplane1 --role control-plane | \ oi component inject --name controlplane2 --role control-plane | \ oi component inject --name controlplane3 --role control-plane | \ oi component inject --name loadbalancer --role control-plane-ingress | \ oi reconcile | \ tee simple-cluster.conf | # so you can inspect the simple-cluster.conf afterwards :-) \ oi cluster admin-kubeconfig > ~/.kube/config
And access it:
$ kubectl 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.
Joining worker nodes to a cluster
You can read more details about the worker joining process here .
License
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.
以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
App研发录:架构设计、Crash分析和竞品技术分析
包建强 / 机械工业出版社 / 2015-10-21 / CNY 59.00
本书是作者多年App开发的经验总结,从App架构的角度,重点总结了Android应用开发中常见的实用技巧和疑难问题解决方法,为打造高质量App提供有价值的实践指导,迅速提升应用开发能力和解决疑难问题的能力。本书涉及的问题有:Android基础建设、网络底层框架设计、缓存、网络流量优化、制定编程规范、模块化拆分、Crash异常的捕获与分析、持续集成、代码混淆、App竞品技术分析、项目管理和团队建设等......一起来看看 《App研发录:架构设计、Crash分析和竞品技术分析》 这本书的介绍吧!