Istio-operator

Istio-operator is a Kubernetes operator to deploy and manage Istio resources for a Kubernetes cluster.

Overview

Istio is an open platform to connect, manage, and secure microservices and it is emerging as the standard for building service meshes on Kubernetes. It is built out on multiple components and a rather complex deployment scheme (around 14 Helm subcharts and 50+ CRDs). Installing, upgrading and operating these components requires deep understanding of Istio and Helm (the standard/supported way of deploying Istio).

The goal of the Istio-operator is to automate and simplify these and enable popular service mesh use cases (multi cluster federation, canary releases, resource reconciliation, etc) by introducing easy higher level abstractions.

Motivation

At Banzai Cloud we are building a Kubernetes distribution, PKE and platform, Pipeline and operate managed Istio clusters for our customers. While we were comfortably operating Istio using the standard Helm deployments on 6 cloud providers and on-premise with Pipeline, recently our customers were asking for multi-cloud and hybrid-cloud service mesh deployments. This required lots of configurations, manual interventions during scaling or removing clusters from the mesh and become an operational burden. Pipeline automates the whole Kubernetes experience (from creating clusters, centralized logging, federated monitoring, multi-dimensional autoscaling, disaster recovery, security scans, etc) and we needed a way to automagically operate Istio across multiple clouds and on-premise hybrid-cloud environments.

At the same time there is a huge interest in the Istio community for an operator, but due to resource constraints and the need of supporting Helm, building one it was discarded. There were several initiatives to simplify Istio:

however, none of these gave a full solution to automate the Istio experience and make it consumable for the wider audience. Our motivation is to build an open source solution and a community which drives the innovation and features of this operator.

If you are willing to kickstart your Istio experience using Pipeline, check out the free developer beta:

Installation

The operator (release-1.4 branch) installs the 1.4.2 version of Istio, and can run on Minikube v1.1.1+ and Kubernetes 1.13.0+.

As a pre-requisite it needs a Kubernetes cluster (you can create one using Pipeline).

Set KUBECONFIG pointing towards your cluster
Run make deploy (deploys the operator in the istio-system namespace to the cluster)
Set your Istio configurations in a Kubernetes custom resource (sample: config/samples/istio_v1beta1_istio.yaml) and run this command to deploy the Istio components:

kubectl create -n istio-system -f config/samples/istio_v1beta1_istio.yaml

Installation with Helm

Alternatively, if you just can’t let go of Helm completely, you can deploy the operator using a Helm chart, which is available in the Banzai Cloud stable Helm repo:

helm repo add banzaicloud-stable https://kubernetes-charts.banzaicloud.com/
helm install --name=istio-operator --namespace=istio-system banzaicloud-stable/istio-operator

Installation with Kustomize

You can also have your own kustomization.yaml file with a reference to Istio operator as a base without the need to clone the repo. See more info in the Kustomize usage doc.

bases:
  - github.com/banzaicloud/istio-operator/config?ref=release-1.4
  - github.com/banzaicloud/istio-operator/config/overlays/auth-proxy-enabled?ref=release-1.4

Installation with Backyards

Go grab and install the Backyards CLI tool.

backyards istio install

Istio upgrade

Check out the upgrade docs to see how to upgrade between minor or major Istio versions.

Multi-cluster federation

Check out the multi-cluster federation docs.

Development

Check out the developer docs.

Uninstall

To remove Istio and Istio operator completely from your cluster execute the following steps:

Delete the Istio configuration custom resource you have created earlier (Istio operator will take care of deleting all Istio resources from your cluster after the custom resource is deleted)
Delete the istio-system namespace to delete Istio operator itself

kubectl delete -n istio-system -f config/samples/istio_v1beta1_istio.yaml
kubectl delete namespace istio-system

Issues, feature requests and roadmap

Please note that the Istio operator is constantly under development and new releases might introduce breaking changes. We are striving to keep backward compatibility as much as possible while adding new features at a fast pace. Issues, new features or bugs are tracked on the projects GitHub page - please feel free to add yours!

To track some of the significant features and future items from the roadmap please visit the roadmap doc.

Contributing

If you find this project useful here's how you can help:

Send a pull request with your new features and bug fixes
Help new users with issues they may encounter
Support the development of this project and star this repo!

Community

If you have any questions about the Istio operator, and would like to talk to us and the other members of the Banzai Cloud community, please join our #istio-operator channel on Slack.

License

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.

dongjiang1989 / istio-operator Goto Github PK

istio-operator's Introduction