![]() !!!note "use ServiceName/ServicePort in forward Action" The action-name in the annotation must match the serviceName in the Ingress rules, and servicePort must be use-annotation.ĪRN can be used in forward action(both simplified schema and advanced schema), it must be an targetGroup created outside of k8s, typically an targetGroup for legacy application. Annotations NameĪlb./load-balancer-nameĪlb./ip-address-typeĪlb./security-groupsĪlb./manage-backend-security-group-rulesĪlb./customer-owned-ipv4-poolĪlb./load-balancer-attributesĪlb./shield-advanced-protectionĪlb./certificate-arnĪlb./backend-protocolĪlb./backend-protocol-versionĪlb./target-group-attributesĪlb./healthcheck-portĪlb./healthcheck-protocolĪlb./healthcheck-pathĪlb./healthcheck-interval-secondsĪlb./healthcheck-timeout-secondsĪlb./healthy-threshold-countĪlb./unhealthy-threshold-countĪlb./auth-idp-cognitoĪlb./auth-on-unauthenticated-requestĪlb./auth-session-cookieĪlb./auth-session-timeoutĪlb./actions.$ Provides a method for configuring custom actions on a listener, such as Redirect Actions. ![]() Merge: such annotation can be specified on all Ingresses within IngressGroup, and will be merged together. Exclusive: such annotation should only be specified on a single Ingress within IngressGroup or specified with same value across all Ingresses within IngressGroup. MergeBehavior column below indicates how such annotation will be merged. Annotations that configures LoadBalancer / Listener behaviors have different merge behavior when IngressGroup feature is been used. Location column below indicates where that annotation can be applied to. Annotations applied to Service have higher priority over annotations applied to Ingress. Advanced format should be encoded as below: ![]() Annotation keys and values can only be strings. You can add annotations to kubernetes Ingress and Service objects to customize their behavior. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |