{"id":52591,"date":"2025-09-09T01:53:59","date_gmt":"2025-09-09T01:53:59","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=52591"},"modified":"2025-09-09T01:58:52","modified_gmt":"2025-09-09T01:58:52","slug":"kubernetes-understanding-ingressclassparams-ingressclass-ingress","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/kubernetes-understanding-ingressclassparams-ingressclass-ingress\/","title":{"rendered":"Kubernetes: Understanding IngressClassParams, IngressClass & Ingress"},"content":{"rendered":"\n

<\/p>\n\n\n\n

\n\n\n\n

1. Understanding the Role of Each Resource<\/h2>\n\n\n\n

IngressClassParams<\/strong><\/h3>\n\n\n\n

A Custom Resource Definition (CRD)<\/strong> used with the AWS Load Balancer Controller. It defines AWS-specific settings for your ALB\u2014like scheme (internet-facing\/internal), IP address type (IPv4 or dualstack), tags, and grouping.<\/p>\n\n\n\n


Template example:<\/p>\n\n\n

apiVersion: elbv2.k8s.aws\/v1beta1\nkind: IngressClassParams\nmetadata:\n  name: alb\nspec:\n  scheme: internet-facing\n  ipAddressType: ipv4\n  tags:\n    - key: env\n      value: dev\n<\/code><\/span><\/pre>\n\n\n
This instructs the AWS ALB controller how to configure the load balancer.
(kubernetes-sigs.github.io<\/a>, AWS Documentation<\/a>)<\/p>\n\n\n\n
\n\n\n\n
IngressClass<\/strong><\/h3>\n\n\n\n
A standard Kubernetes object that tells the cluster who<\/em> manages Ingress resources. It references the IngressClassParams<\/code> and names the AWS controller responsible for provisioning the ALB.<\/p>\n\n\n
apiVersion: networking.k8s.io\/v1\nkind: IngressClass\nmetadata:\n  name: alb\n  annotations:\n    ingressclass.kubernetes.io\/is-default-class: \"true\"\nspec:\n  controller: eks.amazonaws.com\/alb\n  parameters:\n    apiGroup: eks.amazonaws.com\n    kind: IngressClassParams\n    name: alb\n<\/code><\/span><\/pre>\n\n\n
This links your Ingress resources to the right AWS-specific settings.
(AWS Documentation<\/a>, kubernetes-sigs.github.io<\/a>)<\/p>\n\n\n\n
\n\n\n\n
Ingress<\/strong><\/h3>\n\n\n\n
The user-facing Kubernetes object that defines HTTP routing rules\u2014like host, paths, and backend services. It refers to the IngressClass<\/code> by name (unless one is marked default).<\/p>\n\n\n
apiVersion: networking.k8s.io\/v1\nkind: Ingress\nmetadata:\n  name: my-app-ingress\nspec:\n  ingressClassName: alb              # Connects to your IngressClass<\/span>\n  rules:\n    - host: myapp.example.com\n      http:\n        paths:\n          - path: \/\n            pathType: Prefix\n            backend:\n              service:\n                name: my-app-service\n                port:\n                  number: 80<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
2. High-Level Flow (Step-by-Step)<\/h2>\n\n\n\n
    \n
  1. Deploy AWS Load Balancer Controller<\/strong> on your cluster via Helm or manifests (not covered here, but essential).<\/li>\n\n\n\n
  2. Create IngressClassParams<\/strong> \u2192 defines ALB behavior.<\/li>\n\n\n\n
  3. Create IngressClass<\/strong> \u2192 registers a class that uses the AWS controller and links to the params.<\/li>\n\n\n\n
  4. Deploy Ingress resources<\/strong> \u2192 use the class to route traffic; AWS controller builds the ALB behind the scenes.
    (    AWS Documentation<\/a>, Amazon Web Services, Inc.<\/a>)<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n
    3. Best Beginner Tutorials<\/h2>\n\n\n\n
Once applied, AWS provisions an ALB to route traffic as specified.
(AWS Documentation<\/a>, solo.io<\/a>)<\/p>\n\n\n\n