Class ListenerSet

  • All Implemented Interfaces:
    Editable<ListenerSetBuilder>, HasMetadata, KubernetesResource, Namespaced, Serializable

    @Generated("io.fabric8.kubernetes.schema.generator.model.ModelGenerator")
    public class ListenerSet
    extends Object
    implements Editable<ListenerSetBuilder>, HasMetadata, Namespaced
    ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


    The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


    Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


    Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


    ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


    Gateway Integration:

    - The parent Gateway's status will include "AttachedListenerSets"

    which is the count of ListenerSets that have successfully attached to a Gateway

    A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

    - The ListenerSet is selected by the Gateway's AllowedListeners field

    - The ListenerSet has a valid ParentRef selecting the Gateway

    - The ListenerSet's status has the condition "Accepted: true"

    See Also:
    Serialized Form
    • Method Detail

      • getApiVersion

        public String getApiVersion()
        APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
        Specified by:
        getApiVersion in interface HasMetadata
      • setApiVersion

        public void setApiVersion​(String apiVersion)
        APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
        Specified by:
        setApiVersion in interface HasMetadata
      • getKind

        public String getKind()
        Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
        Specified by:
        getKind in interface HasMetadata
      • setKind

        public void setKind​(String kind)
        Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
      • getMetadata

        public ObjectMeta getMetadata()
        ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


        The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


        Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


        Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


        ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


        Gateway Integration:

        - The parent Gateway's status will include "AttachedListenerSets"

        which is the count of ListenerSets that have successfully attached to a Gateway

        A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

        - The ListenerSet is selected by the Gateway's AllowedListeners field

        - The ListenerSet has a valid ParentRef selecting the Gateway

        - The ListenerSet's status has the condition "Accepted: true"

        Specified by:
        getMetadata in interface HasMetadata
      • setMetadata

        public void setMetadata​(ObjectMeta metadata)
        ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


        The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


        Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


        Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


        ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


        Gateway Integration:

        - The parent Gateway's status will include "AttachedListenerSets"

        which is the count of ListenerSets that have successfully attached to a Gateway

        A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

        - The ListenerSet is selected by the Gateway's AllowedListeners field

        - The ListenerSet has a valid ParentRef selecting the Gateway

        - The ListenerSet's status has the condition "Accepted: true"

        Specified by:
        setMetadata in interface HasMetadata
      • getSpec

        public ListenerSetSpec getSpec()
        ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


        The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


        Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


        Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


        ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


        Gateway Integration:

        - The parent Gateway's status will include "AttachedListenerSets"

        which is the count of ListenerSets that have successfully attached to a Gateway

        A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

        - The ListenerSet is selected by the Gateway's AllowedListeners field

        - The ListenerSet has a valid ParentRef selecting the Gateway

        - The ListenerSet's status has the condition "Accepted: true"

      • setSpec

        public void setSpec​(ListenerSetSpec spec)
        ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


        The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


        Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


        Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


        ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


        Gateway Integration:

        - The parent Gateway's status will include "AttachedListenerSets"

        which is the count of ListenerSets that have successfully attached to a Gateway

        A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

        - The ListenerSet is selected by the Gateway's AllowedListeners field

        - The ListenerSet has a valid ParentRef selecting the Gateway

        - The ListenerSet's status has the condition "Accepted: true"

      • getStatus

        public ListenerSetStatus getStatus()
        ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


        The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


        Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


        Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


        ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


        Gateway Integration:

        - The parent Gateway's status will include "AttachedListenerSets"

        which is the count of ListenerSets that have successfully attached to a Gateway

        A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

        - The ListenerSet is selected by the Gateway's AllowedListeners field

        - The ListenerSet has a valid ParentRef selecting the Gateway

        - The ListenerSet's status has the condition "Accepted: true"

      • setStatus

        public void setStatus​(ListenerSetStatus status)
        ListenerSet defines a set of additional listeners to attach to an existing Gateway. This resource provides a mechanism to merge multiple listeners into a single Gateway.


        The parent Gateway must explicitly allow ListenerSet attachment through its AllowedListeners configuration. By default, Gateways do not allow ListenerSet attachment.


        Routes can attach to a ListenerSet by specifying it as a parentRef, and can optionally target specific listeners using the sectionName field.


        Policy Attachment: - Policies that attach to a ListenerSet apply to all listeners defined in that resource - Policies do not impact listeners in the parent Gateway - Different ListenerSets attached to the same Gateway can have different policies - If an implementation cannot apply a policy to specific listeners, it should reject the policy


        ReferenceGrant Semantics: - ReferenceGrants applied to a Gateway are not inherited by child ListenerSets - ReferenceGrants applied to a ListenerSet do not grant permission to the parent Gateway's listeners - A ListenerSet can reference secrets/backends in its own namespace without a ReferenceGrant


        Gateway Integration:

        - The parent Gateway's status will include "AttachedListenerSets"

        which is the count of ListenerSets that have successfully attached to a Gateway

        A ListenerSet is successfully attached to a Gateway when all the following conditions are met:

        - The ListenerSet is selected by the Gateway's AllowedListeners field

        - The ListenerSet has a valid ParentRef selecting the Gateway

        - The ListenerSet's status has the condition "Accepted: true"

      • getAdditionalProperties

        public Map<String,​Object> getAdditionalProperties()
      • setAdditionalProperty

        public void setAdditionalProperty​(String name,
                                          Object value)
      • setAdditionalProperties

        public void setAdditionalProperties​(Map<String,​Object> additionalProperties)