Why do migrated custom ALBs use NGINX instead of Traefik?
Virtual Private Cloud
After you migrate a Classic cluster to VPC, the default Ingress application load balancers (ALBs) run Traefik, but the custom ALBs that were carried over from the Classic cluster still run NGINX.
After migration, your VPC cluster is in a mixed state. When you list the ALBs, the default ALBs run a Traefik version (3.X.X_XXXX_iks), while custom ALBs run an NGINX version (0.X.X_XXXX_iks or 1.X.X_XXXX_iks,
for example 1.15.10_373802345_iks).
Default ALBs in VPC clusters are provisioned with Traefik. Custom ALBs that were migrated from the Classic cluster continue to run NGINX build images.
In a VPC cluster, each public and each private ALB has a single host, so the ALBs can point directly to their respective Traefik instances. To resolve the issue, replace the NGINX build image of each custom ALB with a Traefik build image. Then, update your Ingress resources to use the Traefik Ingress classes.
-
List the available ALB versions and note the latest Traefik version (format
3.X.X_XXXX_iks) from thesupportedTraefikVersionslist ordefaultTraefikVersion. You can optionally specify the--regionflag to check a specific region.ibmcloud ks ingress alb versions --output jsonExample output:
{ "defaultK8sVersion": "1.15.10_379572403_iks", "defaultTraefikVersion": "3.7.13_379020891_iks", "supportedK8sVersions": [ "1.15.10_379572403_iks" ], "k8sStatus": "ga", "supportedTraefikVersions": [ "3.7.12_379572444_iks", "3.7.13_379020891_iks", "3.7.14_379840236_iks" ], "traefikStatus": "ga" } -
List the ALBs in your cluster and identify the ones that run an NGINX version. Check both public and private ALBs.
ibmcloud ks ingress alb ls --cluster CLUSTER_NAME_OR_IDIn the CLI output, check the Build column. ALBs with a build version that starts with
0.or1.run NGINX. ALBs with a version that starts with3.run Traefik.Alternatively, you can review ALB versions and health in the console:
- From the IBM Cloud Kubernetes Service clusters console, select your VPC cluster.
- In the navigation menu, select Ingress.
- Select the Ingress Controllers (ALB) tab.
- In the table, review the Build, Status, and Type columns. ALBs running NGINX display a Build version starting with
0.or1.(for example1.15.10_373802345_iks) and might show a Warning status. ALBs running Traefik display a Build version starting with3.(for example3.7.13_379020891_iks) and show a Healthy status.
-
Disable each ALB that runs NGINX. Repeat this step for each NGINX ALB.
ibmcloud ks ingress alb disable --alb ALB_ID --cluster CLUSTER_NAME_OR_ID -
Re-enable the ALB with the Traefik build image. Replace
TRAEFIK_VERSIONwith the latest3.X.X_XXXX_iksversion from step 1. Repeat this step for each ALB that you disabled.ibmcloud ks ingress alb enable vpc-gen2 --alb ALB_ID --cluster CLUSTER_NAME_OR_ID --version TRAEFIK_VERSION -
After the ALBs report as healthy, verify that the load balancer backend points to Traefik.
ibmcloud ks ingress load-balancer get --cluster CLUSTER_NAME_OR_ID --output jsonExample output when both public and private ALBs are enabled:
{ "cluster": "db365cm209tmvo64q6g0", "backend": { "private": "traefik", "public": "traefik" } }Example output when only the public ALB is enabled:
{ "cluster": "db365cm209tmvo64q6g0", "backend": { "public": "traefik" } } -
Verify that all ALBs in the cluster run a Traefik version. If they do, update the
ingressClassNamein all Ingress resources across all namespaces that don't already use a Traefik Ingress class. For namespace-scoped Ingress resources, you must specify the class explicitly.- For public Ingress, use
public-iks-traefik. - For private Ingress, use
private-iks-traefik.
- For public Ingress, use
For more information about Ingress classes, see Ingress class.