This week I tried testing more NGINX features using annotations and ConfigMap, and seen how they may be applied to applications, and their usabilities.
- Created an HTTPS Ingress controller on AKS with dynamic public IP address. The IP address could be used to route traffic to multiple services in the Kubernetes cluster.
- Used TLS with own certificate, then created Kubernetes secret to use with Ingress route, so the application is accessible from the single IP address.
- I read about configuring HPCC TLS with Jetstack cert manager, then followed the tutorial
- Learned about sticky sessions (Session persistence), for enabling the loadbalancer to create an affinity for the user and server for the time spent on a website (used eclwatch website IP).
- Ran time/run for Ingress, ingress with tls, and eclwatch, and saved the outputs in order to compare user-end and compile time for different services.
- I used sticky session NGINX controller annotations, and tested it for eclwatch and Ingress.
- Tested rate limiting Ingress annotations for eclwatch, define limits for number of accepted requests on given IP per specified time
- Read about NGINX canary annotations feature, uses.
- Tested Ingress canary annotations feature, using eclqueries and eclwatch (application eclqueries is released incrementally to a small subset of users, eclwatch is deployed to the larger set of users)
- Tried whitelist source range annotation feature to specify allowed Client ID source ranges
