Skip to content

Instantly share code, notes, and snippets.

@renuka-fernando

renuka-fernando/choreo-connect-v1.0.0-helm-get-started.md

Last active April 25, 2022 03:14
Show Gist options
  • Save renuka-fernando/26c82a9aaed8ac0ca17249693cec9809 to your computer and use it in GitHub Desktop.
Save renuka-fernando/26c82a9aaed8ac0ca17249693cec9809 to your computer and use it in GitHub Desktop.
Download ZIP
Updated helm chart version for Choreo Connect
Raw
choreo-connect-v1.0.0-helm-get-started.md

Kubernetes (Helm)

Prerequisites

  1. Install Helm and Kubernetes client in order to run the steps provided in the following quick start guide.
  2. An already setup Kubernetes cluster.
  3. Install NGINX Ingress Controller.
  4. Add the WSO2 Helm chart repository. 
    helm repo add wso2 https://helm.wso2.com && helm repo update

Helm V2

Choreo Connect Standalone Deployment

Deploy Choreo Connect in Standalone mode.

helm install --name <RELEASE_NAME> wso2/choreo-connect --version 1.0.0-2 --namespace <NAMESPACE>

Endpoints

Obtain the external IP (EXTERNAL-IP) of the Ingress resources by listing down the Kubernetes Ingresses.

kubectl get ing -n <NAMESPACE>

Add the above host as an entry in /etc/hosts file as shown below:

<EXTERNAL-IP>    adapter.wso2.com
<EXTERNAL-IP>    gw.wso2.com

Follow the document Deploying a REST API in Choreo Connect to deploy an API.

Helm V3

Choreo Connect Standalone Deployment

Deploy Choreo Connect in Standalone mode.

helm install <RELEASE_NAME> wso2/choreo-connect --version 1.0.0-2 --namespace <NAMESPACE> --create-namespace

Endpoints

Obtain the external IP (EXTERNAL-IP) of the Ingress resources by listing down the Kubernetes Ingresses.

kubectl get ing -n <NAMESPACE>

Add the above host as an entry in /etc/hosts file as shown below:

<EXTERNAL-IP>    adapter.wso2.com
<EXTERNAL-IP>    gw.wso2.com

Follow the document Deploying a REST API in Choreo Connect to deploy an API.

Choreo Connect - API Manager as Control Plane

Please refer to the following documentation Deploying Choreo Connect on Kubernetes With WSO2 API Manager as a Control Plane for more information.

Raw
choreo-connect-v1.1.0-helm-get-started.md

Kubernetes (Helm)

Prerequisites

  1. Install Helm and Kubernetes client in order to run the steps provided in the following quick start guide.
  2. An already setup Kubernetes cluster.
  3. Install NGINX Ingress Controller.
  4. Add the WSO2 Helm chart repository. 
    helm repo add wso2 https://helm.wso2.com && helm repo update

Helm V2

Choreo Connect Standalone Deployment

Deploy Choreo Connect in Standalone mode.

helm install --name <RELEASE_NAME> wso2/choreo-connect --version 1.1.0-1 --namespace <NAMESPACE>

Endpoints

Obtain the external IP (EXTERNAL-IP) of the Ingress resources by listing down the Kubernetes Ingresses.

kubectl get ing -n <NAMESPACE>

Add the above host as an entry in /etc/hosts file as shown below:

<EXTERNAL-IP>    adapter.wso2.com
<EXTERNAL-IP>    gw.wso2.com

Follow the document Deploying a REST API in Choreo Connect to deploy an API.

Helm V3

Choreo Connect Standalone Deployment

Deploy Choreo Connect in Standalone mode.

helm install <RELEASE_NAME> wso2/choreo-connect --version 1.1.0-1 --namespace <NAMESPACE> --create-namespace

Endpoints

Obtain the external IP (EXTERNAL-IP) of the Ingress resources by listing down the Kubernetes Ingresses.

kubectl get ing -n <NAMESPACE>

Add the above host as an entry in /etc/hosts file as shown below:

<EXTERNAL-IP>    adapter.wso2.com
<EXTERNAL-IP>    gw.wso2.com

Follow the document Deploying a REST API in Choreo Connect to deploy an API.

Choreo Connect - API Manager as Control Plane

Please refer to the following documentation Deploying Choreo Connect on Kubernetes With WSO2 API Manager as a Control Plane for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment