Multi-Cluster Design with F5 Container Ingress Services
Summary
The Multi-Cluster Design is an F5 Alliances product showcase and will be part of the F5 Provisioner in the near future. This is built by F5 Business Development organization.
Goal
The Purpose of the multi cluster use case is to show how F5 Container Ingress Services can be used in conjunction with several other F5 Alliances integrations to demonstrate conducting an A/B deployment of a web application.
Design Overview
Prerequisites
Currently some of the set up for this Design is a manual process. A method to build these POC environments via the F5 Provisioner is in progress. For this learning material you will need several prerequisites in place to begin.
- Access to git preferable a valid GitHub account
- A Jenkins Server
- A minimum of two OpenShift clusters
- Two Licensed BIG-IP VE appliances with Best licenses, one per cluster
- F5 Container Ingress Service - Installed
- Access to F5 Cloud Services (DNS Load Balancing)
Optional Features
- Access to Equinix Smart Key
Getting started
Once the necessary servers and infrastructure are in place users will be able to run through the automation scenarios via Jenkins to demonstrate an A/B deployment scenario.
The Multi-Cluster Design can be used:
- as a self learning tool to get familiar with OpenShift & Container Ingress Services for F5 BIG-IP
- as a self learning tool to get familiar with Jenkins for Continual Deployment
- to build demos and proof of concepts
- to understand:
- Ansible Automation
- Application Services 3
- F5AAS Service DNS load balancing
- F5 Integration with Equinix Smartkey
Follow Getting Started for detailed steps on how to build out the A / B Deployment setup.
Support
This project is a community effort to promote container ingress service automation and is maintained by F5 BD. For any feature requests or issues, feel free to open an issue and we will give our best effort to address it.