In this section, we test our first environment of WSO2 Microgateway.
The Jenkins Dashboard can be accessed through https://jenkins. Thereafter, log in with the default username and password, which are “admin” and “admin”, and select “wso2mgw”.
Trigger the job push-chart-to-spinnaker
Explore the Spinnaker Dashboard.
Navigate to the Spinnaker dashboard at https://spinnaker and select Applications > wso2mgw > Pipelines.
The Spinnaker dashboard shows the progress of the deployment. You are presented with three pipelines where one is active.
Deploy Dev: Pipeline is responsible for executing the tasks in deploying the changes to Dev environment.
Deploy Staging: Pipeline responsible for executing the tasks in deploying the changes to the Staging environment.
Deploy Prod: Pipeline responsible for executing the tasks in deploying the changes to the Production environment.
Once the changes have been deployed to the Dev environment, you will be prompted to provide a manual input in order to proceed to make a deployment to Staging.Image Modified
Before proceeding with the manual judgment, let us examine our WSO2 API Microgateway in the Dev environment. Navigate to Infrastructure tab > Load Balancers tab> ingress wso2micro-gw-ingress
Ingress information of current deployments can be observed here. The Ingress IP address of the Microgateway Dev environment can be obtained from the sidebar to the right.