wso2 / kubernetes-open-banking Goto Github PK

Description:
Currently Helm Charts are available only for simplified patterns of WSO2 OB solution. To create high availability deployments, Helm charts will have to be created for patterns 4 as well.

Description:
It is required to perform $subject for Helm resources of the following product deployment patterns.

Sub Tasks:

• Documentation for deployment pattern 1
• Documentation for deployment pattern 3
• Code/Peer review

Description:
It is required to perform $subject for Open Banking API Manager with Key Manager support and high availability.

Description:
Create resources for a Helm Chart which performs a single node deployment of the Open Banking Solution pattern 2.

Sub tasks:

• Define deployment definitions for the product profiles (refer #15 and #16)
• Define service definitions to expose the product profile services within the cluster (refer #19 and #20)
• Expose the necessary product profile services to outside of the cluster (refer #18)

Description:
Add a README for the using the Helm Chart created to deploy WSO2 Open Banking Deployment pattern 1 on Kubernetes

Description:
Currently Helm Charts are available only for simplified patterns of WSO2 OB solution. To create high availability deployments, Helm charts will have to be created for patterns 5 as well.

Description:
Add Ingress support for the relevant WSO2 Open Banking Business Intelligence Dashboad services, to expose them outside of the Kubernetes cluster.

It is expected to use the NGINX Ingress Controller [1], for this purpose.

[1]: NGINX Ingress Controller maintained by Kubernetes

Description:
Currently WSO2 Open Banking Kubernetes artifacts support only one specification (i.e Berlin). In future there might be a requirement for the K8s artifacts to support multiple specifications.

We already have an approach as follows.

Folder Structure:

kubernetes-open-banking
|--database
   |--mysql-ob
   |--mysql-ob-berlin
   |--mysql-ob-uk

Here we use all the specification related scripts inside relevant folders such as mysql-ob-berlin and mysql-ob-uk. These chart folders contains a MySQL base chart inside their charts directory. Then we package both these specification based database charts inside common mysql-ob chart. Relevant conditions in the requirements.yaml file in mysql-ob chart will determine which sub-chart (either mysql-ob-berlin or mysql-ob-uk) to deploy in the deployment time.

Description:
Currently WSO2 Open Banking Helm Charts support only internal NFS support. Values.yaml file of both patterns will have to be edited to support external NFS as well

Description:
We have changed product names from Key Manager to Identity & Access Management Module in OB 2.0 release, Currently we used km which stands for Key Manager instead of iam which stands for Identity & Access Management. We have used this reference in several places including Kubernetes and Helm resources. Therefore we have to refactor previously used product names to cater for new changes.

Description:
The $subject needs to be performed as Azure Files is one of the most popular storage options available and supports ReadWriteMany access mode.

Documentation:
Use official Azure guides for dynamic provisioning and manual provisioning

Sub Tasks:

• Add instructions for installation if considered suitable
• Update WSO2 Product container guide with results (refer to wso2/container-guide#17)

Description:
Create a CHANGELOG.md for the repo

Description:
Add contributors.md file to the repo and update the title of the repo to match with title of other similar WSO2 products[1].

[1] https://github.com/wso2/kubernetes-apim

Description:
Create Kubernetes artifacts for WSO2 Open Banking Key Manager service. For this purpose, Kubernetes Service [1] definition(s) need to be defined.

[1]: Kubernetes Service

Description:
Add Ingress support for the relevant WSO2 Open Banking API Manager services, to expose them outside of the Kubernetes cluster.

It is expected to use the NGINX Ingress Controller [1], for this purpose.

[1]: NGINX Ingress Controller maintained by Kubernetes

Description:
Introduce the metadata (.metadata) file required by the WSO2 Infrastructure Resource Generator for migrating the Kubernetes and Helm resources between product versions.

Create Kubernetes artifacts for WSO2 Open Banking Business Intelligence Dashboard Deployment.

Description:
Currently, Helm Charts are available only for UK spec for pattern 2 of WSO2 OB solution. Helm Chart for WSO2 Open Banking Solution Deployment Pattern 2 for Berlin Spec will have to be created as well.

Description:
Create Kubernetes artifacts for WSO2 Open Banking API Manager service. For this purpose, Kubernetes Service [1] definition(s) need to be defined.

[1]: Kubernetes Service

Description:
Currently, the evaluatory MySQL deployment refers to 5.7 stable image tag of official MySQL Docker image tag.

It is ideal to refer to a specific, unique MySQL Docker image tag (e.g. 5.7.31) mapping to an update of MySQL. This provides us the knowledge of the exact MySQL update level up to which product Helm charts have been tested with.

Affected Product Version:
Kubernetes and Helm Resources for WSO2 Open Banking version 1.5.0.1 and above

Description:
In general, Google Kubernetes Engine (GKE) is used as the development Kubernetes environment for Kubernetes/Helm resources.

WSO2 Open Banking Kubernetes/Helm resources need to be tested with AWS AKS managed service.

Related Issues:
#57

Description:
The $subject needs to be introduced for the purpose of evaluation of Open Banking product Helm charts.

Description:
Create Kubernetes artifacts for WSO2 Open Banking Business Intelligence Worker service. For this purpose, Kubernetes Service [1] definition(s) need to be defined.

[1]: Kubernetes Service

Description:
It is required to perform $subject for Helm resources of the following product deployment patterns.

Documentation for deployment pattern 2

Description:
Currently, MySQL based WSO2 Helm charts use version 1.6.7. This needs to be upgraded.

Description:
Add Ingress support for the WSO2 Open Banking Key Manager service, to expose it outside of the Kubernetes cluster.

It is expected to use the NGINX Ingress Controller [1], for this purpose.

[1]: NGINX Ingress Controller maintained by Kubernetes

Description:
Use Stable MySQL Helm Chart available at https://github.com/helm/charts/tree/master/stable/mysql to create the relevant Helm Chart for OB solution.

Description:
Currently, MySQL based WSO2 Helm charts use version 1.4.0. This needs to be upgraded.

Please see the link for stable MySQL Helm chart versions.

Description:
It is required to perform $subject for Open Banking API Manager with Key Manager and Business Intelligence support and high availability.

Description:
Create Kubernetes artifacts for WSO2 Open Banking Key Manager service. For this purpose, Kubernetes Service [1] definition(s) need to be defined.

[1]: Kubernetes Service

Description:
The prefix "simplified" is not added to the folder names eventhough it is present in the chart names. This needs to be fixed

Description:
Currently Helm Charts are available only for simplified patterns of WSO2 OB solution. To create high availability deployments, Helm charts will have to be created for patterns 3 as well.

Create Kubernetes artifacts for WSO2 Open Banking Business Intelligence Worker profile

Description:
It is required to perform $subject for Open Banking API Manager with Identity & Access Management Module and Business Intelligence support with high availability.

Description:
Create Kubernetes artifacts for deploying WSO2 Open Banking Key Manager. For deploying the WSO2 Identity Server based Open Banking Key Manager, a Kubernetes Deployment [1] can be used.

[1]: Kubernetes Deployment

Description:
It was understood that we should stick to $subject design since, maintaining a MySQL deployment Helm chart per Open Banking PSD2 API specification would force packaging every database chart in the a product deployment pattern Helm chart.

Related Issues:
#46

Description:
The current helm chart created for deployment pattern 1 does not persist the runtime artifacts. Use NFS provisioner stable helm chart (https://github.com/helm/charts/tree/master/stable/nfs-server-provisioner) to persist them.

Description:
Currently, Helm Charts are available only for UK spec for pattern 1 of WSO2 OB solution. Helm Chart for WSO2 Open Banking Solution Deployment Pattern 1 for Berlin Spec will have to be created as well.

Description:
Create Kubernetes artifacts for deploying WSO2 Open Banking API Manager.

Description:
Create resources for a Helm Chart which performs a single node deployment of the Open Banking Solution.

Sub Tasks:

• Define deployment definitions for the product profiles (refer #2 and #3)
• Define service definitions to expose the product profile services within the cluster (refer #9 and #8)
• Expose the necessary product profile services to outside of the cluster (refer #5 and #4)
• Add Persistent volume support for the setup (refer #17)
• Add a README (refer #14)
• Code/Peer review