tsuresh / wso2-is-k8s-operator

The following CRD operator can be used to deploy WSO2 IS on your Kubernates Cluster

WSO2 Identity Server - K8S Operator

The following CRD operator can be used to deploy WSO2 IS on your Kubernates Cluster. If you want to deploy the Identity Server via Helm operator please refer to the given link: https://github.com/wso2/kubernetes-is

Prerequisites

• Access to a Kubernetes v1.11.3+ cluster (v1.16.0+ if using apiextensions.k8s.io/v1 CRDs).
• User logged with admin permission. See how to grant yourself cluster-admin privileges or be logged in as admin
• Homebrew installed
• Git command line installed and configured

External Database Setup

Please follow the instructions given in the documentation to setup the external MySQL databases

• https://is.docs.wso2.com/en/5.9.0/setup/changing-to-mysql/
• https://is.docs.wso2.com/en/5.9.0/setup/changing-datasource-bpsds/
• https://is.docs.wso2.com/en/5.9.0/setup/changing-datasource-consent-management/

Databases to be created

• WSO2_IDENTITY_DB
• WSO2_SHARED_DB
• WSO2_CONSENT_DB
• WSO2_BPS_DB

Installation [Dev]

Please follow the following instructions to install Operator-SDK in your development environment.

brew install operator-sdk

Clone the repository by running the following command

git clone https://github.com/tsuresh/wso2-is-k8s-operator.git

Run the following command to install dependancies

make install

Navigate to the project directory

cd wso2-is-operator

Apply the CRD by running the following command

kubectl apply -f config/crd/bases/wso2.wso2.com_wso2is.yaml

You are free to change any configurations at config/samples/wso2_v1_wso2is.yaml Once you do the config changes apply the config by running

kubectl apply -f config/samples/wso2_v1_wso2is.yaml

Finally run the following command to run the operator in your cluster

make run

Installation [Prod]

To be released

wso2-is-k8s-operator's Issues

Ability to setup multiple IS Instances in same cluster

If there's a requirement to set up multiple WSO2 IS instances in the same Kubernetes Cluster there should be a mechanism to provision both via the same operator

Proposed method(s)

• Configure the deployments with different namespaces for each deployment

Cleanup all resources after deletion

Cleanup all the resources which have been provisioned after deleting the CRD

The following resources have to be deleted

• Custom namespaces provisioned at issue #1
• Pods
• Services
• Ingress
• Deployments
• Config Maps
• Exernal Databases (Drop)

Add IaaS Load Balancer Ingress Support

Change the controller to support IaaS load balancer support