NGINX Modern Apps latest

Contents:

  • Class 1 - Intro to NGINX Plus
  • Class 2 - NGINX Plus CI/CD Lab
  • Class 3 - NGINX Dataplane Scripting
  • Class 4 - Introduction to NGINX Instance Manager
  • Class 5 - Application Security and Observability with NAP
  • Class 6 - NGINX API Management
  • Class 7 - NGINX Kubernetes Ingress Controller, the new Rancher Manager and Rancher Kubernetes Engine 2
  • Class 8 - Mastering NGINX One: Performance Tuning and Security Hardening Best Practices
  • Class 9: Zero Trust at Scale with F5 NGINX
  • Class 10 - NMS API Connectivity Manager
    • Module 1 - Deploying an API for a modern app
    • Module 2 - Infrastructure team - Deploy Nginx instances
    • Module 3 - API Team - Publish API v1.0
    • Module 4 - Dev Team - Consume API v1.0
    • Module 5 - API Team - Publish API v2.0
    • Module 6 - Dev Team - Consume API v2.0
    • Module 7 - Advanced Security Lab
    • Module 8 - Observability and Monitoring
  • Class 11 - F5 NGINX Plus Ingress Controller as an API Gateway for Kubernetes
  • Class 12 - The Path to Understanding Kubernetes and Containers
  • Class 13 - Maximize ROI with F5 NGINX App Protect(NAP) using Observability
  • Class 14 – Operationalize NGINX One Configuration and Enable Self-Service through Templates
  • Class 16 - Beyond Models: A Practical Guide to Protecting Your AI-Powered Apps
  • Class 17 - Integrating NGINX Ingress Controller with F5 BIG-IP
  • Class 18 - Mastering cloud-native app delivery: Unlocking advanced capabilities and use cases with F5’s ADCaaS (NGINXaaS)

On this page:
  • Step 3 - Link the API GW and Dev Portal
    • Link the API-GW instance
    • Link the Dev-Portal instance
    • Check instances connectivity with NMS
    • Wait for the environment to be GREEN
NGINX Modern Apps > Class 10 - NMS API Connectivity Manager > Module 2 - Infrastructure team - Deploy Nginx instances Source | Edit on

Version notice:

Step 3 - Link the API GW and Dev Portal¶

It is time to link the API-GW and Dev-Portal instances with NMS. To do so, we will execute the Nginx Agent installer on both instances.

Link the API-GW instance¶

  1. In NMS UI, click on the API Cluster Gateway row (not the name link) to pop out the right frame with the commands to execute

    ../../../_images/api-cluster-curl.png
  2. Copy the cURL command; it should look like this

    curl -k https://10.1.1.6/install/nginx-agent > install.sh && sudo sh install.sh -g api-cluster && sudo systemctl start nginx-agent
    

    Warning

    check the FQDN is 10.1.1.6 and not the UDF public proxy FQDN

  3. In UDF, SSH or WEBSSH to NGINX Plus APIGW-1

    ../../../_images/apigw-udf-webshell.png
  4. In the NGINX Plus APIGW-1 SSH session, issue the nginx -T command to get a dump of the full NGINX configuration. Note the relative lack of configuration on the data plane. (If you are seeing permission issues, you may need to utilize SUDO priviliges to execute the nginx -T command.)

    nginx -T
    
  5. In the NGINX Plus APIGW-1 SSH session, paste and execute the cURL command copied from NMS. You will see the below outcome at the end of the installation.

    ----------------------------------------------------------------------
    NGINX Agent package has been successfully installed.
    
    Please follow the next steps to start the software:
    sudo systemctl start nginx-agent
    
    Configuration settings can be adjusted here:
    /etc/nginx-agent/nginx-agent.conf
    
    ----------------------------------------------------------------------
    
    Installing nginx-agent package ... done.
    Updating /etc/nginx-agent/agent-dynamic.conf ...
    Setting existing instance_group: api-cluster
    Successfully updated /etc/nginx-agent/agent-dynamic.conf
    

Link the Dev-Portal instance¶

  1. In the NSM UI, Like the API-GW instance, click the Developer Portal Clusters row and copy the cURL command.

    Warning

    DO NOT CLICK ON Developer Portal Internal Clusters

    ../../../_images/devportal-curl.png
  2. The cURL command should look like this

    curl -k https://10.1.1.6/install/nginx-agent > install.sh && sudo sh install.sh -g devportal-cluster && sudo systemctl start nginx-agent
    

    Warning

    Check that the FQDN is 10.1.1.6 and not the UDF public proxy FQDN

  3. In UDF, SSH or WEBSSH to Dev Portal

    ../../../_images/devportal-udf-webshell.png
  4. In the NGINX Dev-Portal SSH session, again issue the nginx -T command to get a dump of the full NGINX configuration.

    nginx -T
    
  5. On the NGINX Dev-Portal SSH session, paste and execute the cURL command. You will see the below outcome at the end of the installation.

    ----------------------------------------------------------------------
    NGINX Agent package has been successfully installed.
    
    Please follow the next steps to start the software:
    sudo systemctl start nginx-agent
    
    Configuration settings can be adjusted here:
    /etc/nginx-agent/nginx-agent.conf
    
    ----------------------------------------------------------------------
    
    Installing nginx-agent package ... done.
    Could not find /etc/nginx-agent/agent-dynamic.conf ... Creating file
    Successfully created /etc/nginx-agent/agent-dynamic.conf
    Updating /etc/nginx-agent/agent-dynamic.conf ...
    Setting instance_group: devportal-cluster
    Successfully updated /etc/nginx-agent/agent-dynamic.conf
    

Check instances connectivity with NMS¶

  1. In API Gateway Clusters section, click on name api-cluster

    ../../../_images/env-overview.png
  2. Scroll down and check your API-GW instance is linked and green

    ../../../_images/api-gateway.png
  3. Switch to the Dev-Portal by clicking on the cluster top menu

    ../../../_images/switch-devportal.png
  4. You can see your Nginx DevPortal instance GREEN, but also a way to customize the DevPortal

    ../../../_images/dev-portal-cluster.png

Wait for the environment to be GREEN¶

  1. Switch back to your Infrastructure team-sentence Workspace screen. And check the Job Status

    Note

    If you don’t see the column Job Status, scroll to the right; the column is hidden because of the Win10 RDP low resolution.

  2. Wait till it passes to Success. This can take several minutes.

    ../../../_images/status-pending.png ../../../_images/status-success.png
Previous Next