config/crds/v1/resources/logstash.k8s.elastic.co_logstashes.yaml [8361:8617]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                      properties:
                        metadata:
                          description: |-
                            ObjectMeta is the metadata of the service.
                            The name and namespace provided here are managed by ECK and will be ignored.
                          properties:
                            annotations:
                              additionalProperties:
                                type: string
                              type: object
                            finalizers:
                              items:
                                type: string
                              type: array
                            labels:
                              additionalProperties:
                                type: string
                              type: object
                            name:
                              type: string
                            namespace:
                              type: string
                          type: object
                        spec:
                          description: Spec is the specification of the service.
                          properties:
                            allocateLoadBalancerNodePorts:
                              description: |-
                                allocateLoadBalancerNodePorts defines if NodePorts will be automatically
                                allocated for services with type LoadBalancer.  Default is "true". It
                                may be set to "false" if the cluster load-balancer does not rely on
                                NodePorts.  If the caller requests specific NodePorts (by specifying a
                                value), those requests will be respected, regardless of this field.
                                This field may only be set for services with type LoadBalancer and will
                                be cleared if the type is changed to any other type.
                              type: boolean
                            clusterIP:
                              description: |-
                                clusterIP is the IP address of the service and is usually assigned
                                randomly. If an address is specified manually, is in-range (as per
                                system configuration), and is not in use, it will be allocated to the
                                service; otherwise creation of the service will fail. This field may not
                                be changed through updates unless the type field is also being changed
                                to ExternalName (which requires this field to be blank) or the type
                                field is being changed from ExternalName (in which case this field may
                                optionally be specified, as describe above).  Valid values are "None",
                                empty string (""), or a valid IP address. Setting this to "None" makes a
                                "headless service" (no virtual IP), which is useful when direct endpoint
                                connections are preferred and proxying is not required.  Only applies to
                                types ClusterIP, NodePort, and LoadBalancer. If this field is specified
                                when creating a Service of type ExternalName, creation will fail. This
                                field will be wiped when updating a Service to type ExternalName.
                                More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
                              type: string
                            clusterIPs:
                              description: |-
                                ClusterIPs is a list of IP addresses assigned to this service, and are
                                usually assigned randomly.  If an address is specified manually, is
                                in-range (as per system configuration), and is not in use, it will be
                                allocated to the service; otherwise creation of the service will fail.
                                This field may not be changed through updates unless the type field is
                                also being changed to ExternalName (which requires this field to be
                                empty) or the type field is being changed from ExternalName (in which
                                case this field may optionally be specified, as describe above).  Valid
                                values are "None", empty string (""), or a valid IP address.  Setting
                                this to "None" makes a "headless service" (no virtual IP), which is
                                useful when direct endpoint connections are preferred and proxying is
                                not required.  Only applies to types ClusterIP, NodePort, and
                                LoadBalancer. If this field is specified when creating a Service of type
                                ExternalName, creation will fail. This field will be wiped when updating
                                a Service to type ExternalName.  If this field is not specified, it will
                                be initialized from the clusterIP field.  If this field is specified,
                                clients must ensure that clusterIPs[0] and clusterIP have the same
                                value.

                                This field may hold a maximum of two entries (dual-stack IPs, in either order).
                                These IPs must correspond to the values of the ipFamilies field. Both
                                clusterIPs and ipFamilies are governed by the ipFamilyPolicy field.
                                More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
                              items:
                                type: string
                              type: array
                              x-kubernetes-list-type: atomic
                            externalIPs:
                              description: |-
                                externalIPs is a list of IP addresses for which nodes in the cluster
                                will also accept traffic for this service.  These IPs are not managed by
                                Kubernetes.  The user is responsible for ensuring that traffic arrives
                                at a node with this IP.  A common example is external load-balancers
                                that are not part of the Kubernetes system.
                              items:
                                type: string
                              type: array
                              x-kubernetes-list-type: atomic
                            externalName:
                              description: |-
                                externalName is the external reference that discovery mechanisms will
                                return as an alias for this service (e.g. a DNS CNAME record). No
                                proxying will be involved.  Must be a lowercase RFC-1123 hostname
                                (https://tools.ietf.org/html/rfc1123) and requires `type` to be "ExternalName".
                              type: string
                            externalTrafficPolicy:
                              description: |-
                                externalTrafficPolicy describes how nodes distribute service traffic they
                                receive on one of the Service's "externally-facing" addresses (NodePorts,
                                ExternalIPs, and LoadBalancer IPs). If set to "Local", the proxy will configure
                                the service in a way that assumes that external load balancers will take care
                                of balancing the service traffic between nodes, and so each node will deliver
                                traffic only to the node-local endpoints of the service, without masquerading
                                the client source IP. (Traffic mistakenly sent to a node with no endpoints will
                                be dropped.) The default value, "Cluster", uses the standard behavior of
                                routing to all endpoints evenly (possibly modified by topology and other
                                features). Note that traffic sent to an External IP or LoadBalancer IP from
                                within the cluster will always get "Cluster" semantics, but clients sending to
                                a NodePort from within the cluster may need to take traffic policy into account
                                when picking a node.
                              type: string
                            healthCheckNodePort:
                              description: |-
                                healthCheckNodePort specifies the healthcheck nodePort for the service.
                                This only applies when type is set to LoadBalancer and
                                externalTrafficPolicy is set to Local. If a value is specified, is
                                in-range, and is not in use, it will be used.  If not specified, a value
                                will be automatically allocated.  External systems (e.g. load-balancers)
                                can use this port to determine if a given node holds endpoints for this
                                service or not.  If this field is specified when creating a Service
                                which does not need it, creation will fail. This field will be wiped
                                when updating a Service to no longer need it (e.g. changing type).
                                This field cannot be updated once set.
                              format: int32
                              type: integer
                            internalTrafficPolicy:
                              description: |-
                                InternalTrafficPolicy describes how nodes distribute service traffic they
                                receive on the ClusterIP. If set to "Local", the proxy will assume that pods
                                only want to talk to endpoints of the service on the same node as the pod,
                                dropping the traffic if there are no local endpoints. The default value,
                                "Cluster", uses the standard behavior of routing to all endpoints evenly
                                (possibly modified by topology and other features).
                              type: string
                            ipFamilies:
                              description: |-
                                IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this
                                service. This field is usually assigned automatically based on cluster
                                configuration and the ipFamilyPolicy field. If this field is specified
                                manually, the requested family is available in the cluster,
                                and ipFamilyPolicy allows it, it will be used; otherwise creation of
                                the service will fail. This field is conditionally mutable: it allows
                                for adding or removing a secondary IP family, but it does not allow
                                changing the primary IP family of the Service. Valid values are "IPv4"
                                and "IPv6".  This field only applies to Services of types ClusterIP,
                                NodePort, and LoadBalancer, and does apply to "headless" services.
                                This field will be wiped when updating a Service to type ExternalName.

                                This field may hold a maximum of two entries (dual-stack families, in
                                either order).  These families must correspond to the values of the
                                clusterIPs field, if specified. Both clusterIPs and ipFamilies are
                                governed by the ipFamilyPolicy field.
                              items:
                                description: |-
                                  IPFamily represents the IP Family (IPv4 or IPv6). This type is used
                                  to express the family of an IP expressed by a type (e.g. service.spec.ipFamilies).
                                type: string
                              type: array
                              x-kubernetes-list-type: atomic
                            ipFamilyPolicy:
                              description: |-
                                IPFamilyPolicy represents the dual-stack-ness requested or required by
                                this Service. If there is no value provided, then this field will be set
                                to SingleStack. Services can be "SingleStack" (a single IP family),
                                "PreferDualStack" (two IP families on dual-stack configured clusters or
                                a single IP family on single-stack clusters), or "RequireDualStack"
                                (two IP families on dual-stack configured clusters, otherwise fail). The
                                ipFamilies and clusterIPs fields depend on the value of this field. This
                                field will be wiped when updating a service to type ExternalName.
                              type: string
                            loadBalancerClass:
                              description: |-
                                loadBalancerClass is the class of the load balancer implementation this Service belongs to.
                                If specified, the value of this field must be a label-style identifier, with an optional prefix,
                                e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users.
                                This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load
                                balancer implementation is used, today this is typically done through the cloud provider integration,
                                but should apply for any default implementation. If set, it is assumed that a load balancer
                                implementation is watching for Services with a matching class. Any default load balancer
                                implementation (e.g. cloud providers) should ignore Services that set this field.
                                This field can only be set when creating or updating a Service to type 'LoadBalancer'.
                                Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type.
                              type: string
                            loadBalancerIP:
                              description: |-
                                Only applies to Service Type: LoadBalancer.
                                This feature depends on whether the underlying cloud-provider supports specifying
                                the loadBalancerIP when a load balancer is created.
                                This field will be ignored if the cloud-provider does not support the feature.
                                Deprecated: This field was under-specified and its meaning varies across implementations.
                                Using it is non-portable and it may not support dual-stack.
                                Users are encouraged to use implementation-specific annotations when available.
                              type: string
                            loadBalancerSourceRanges:
                              description: |-
                                If specified and supported by the platform, this will restrict traffic through the cloud-provider
                                load-balancer will be restricted to the specified client IPs. This field will be ignored if the
                                cloud-provider does not support the feature."
                                More info: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/
                              items:
                                type: string
                              type: array
                              x-kubernetes-list-type: atomic
                            ports:
                              description: |-
                                The list of ports that are exposed by this service.
                                More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
                              items:
                                description: ServicePort contains information on service's
                                  port.
                                properties:
                                  appProtocol:
                                    description: |-
                                      The application protocol for this port.
                                      This is used as a hint for implementations to offer richer behavior for protocols that they understand.
                                      This field follows standard Kubernetes label syntax.
                                      Valid values are either:

                                      * Un-prefixed protocol names - reserved for IANA standard service names (as per
                                      RFC-6335 and https://www.iana.org/assignments/service-names).

                                      * Kubernetes-defined prefixed names:
                                        * 'kubernetes.io/h2c' - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior-
                                        * 'kubernetes.io/ws'  - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
                                        * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455

                                      * Other protocols should use implementation-defined prefixed names such as
                                      mycompany.com/my-custom-protocol.
                                    type: string
                                  name:
                                    description: |-
                                      The name of this port within the service. This must be a DNS_LABEL.
                                      All ports within a ServiceSpec must have unique names. When considering
                                      the endpoints for a Service, this must match the 'name' field in the
                                      EndpointPort.
                                      Optional if only one ServicePort is defined on this service.
                                    type: string
                                  nodePort:
                                    description: |-
                                      The port on each node on which this service is exposed when type is
                                      NodePort or LoadBalancer.  Usually assigned by the system. If a value is
                                      specified, in-range, and not in use it will be used, otherwise the
                                      operation will fail.  If not specified, a port will be allocated if this
                                      Service requires one.  If this field is specified when creating a
                                      Service which does not need it, creation will fail. This field will be
                                      wiped when updating a Service to no longer need it (e.g. changing type
                                      from NodePort to ClusterIP).
                                      More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
                                    format: int32
                                    type: integer
                                  port:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



config/crds/v1/resources/maps.k8s.elastic.co_elasticmapsservers.yaml [118:374]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                    properties:
                      metadata:
                        description: |-
                          ObjectMeta is the metadata of the service.
                          The name and namespace provided here are managed by ECK and will be ignored.
                        properties:
                          annotations:
                            additionalProperties:
                              type: string
                            type: object
                          finalizers:
                            items:
                              type: string
                            type: array
                          labels:
                            additionalProperties:
                              type: string
                            type: object
                          name:
                            type: string
                          namespace:
                            type: string
                        type: object
                      spec:
                        description: Spec is the specification of the service.
                        properties:
                          allocateLoadBalancerNodePorts:
                            description: |-
                              allocateLoadBalancerNodePorts defines if NodePorts will be automatically
                              allocated for services with type LoadBalancer.  Default is "true". It
                              may be set to "false" if the cluster load-balancer does not rely on
                              NodePorts.  If the caller requests specific NodePorts (by specifying a
                              value), those requests will be respected, regardless of this field.
                              This field may only be set for services with type LoadBalancer and will
                              be cleared if the type is changed to any other type.
                            type: boolean
                          clusterIP:
                            description: |-
                              clusterIP is the IP address of the service and is usually assigned
                              randomly. If an address is specified manually, is in-range (as per
                              system configuration), and is not in use, it will be allocated to the
                              service; otherwise creation of the service will fail. This field may not
                              be changed through updates unless the type field is also being changed
                              to ExternalName (which requires this field to be blank) or the type
                              field is being changed from ExternalName (in which case this field may
                              optionally be specified, as describe above).  Valid values are "None",
                              empty string (""), or a valid IP address. Setting this to "None" makes a
                              "headless service" (no virtual IP), which is useful when direct endpoint
                              connections are preferred and proxying is not required.  Only applies to
                              types ClusterIP, NodePort, and LoadBalancer. If this field is specified
                              when creating a Service of type ExternalName, creation will fail. This
                              field will be wiped when updating a Service to type ExternalName.
                              More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
                            type: string
                          clusterIPs:
                            description: |-
                              ClusterIPs is a list of IP addresses assigned to this service, and are
                              usually assigned randomly.  If an address is specified manually, is
                              in-range (as per system configuration), and is not in use, it will be
                              allocated to the service; otherwise creation of the service will fail.
                              This field may not be changed through updates unless the type field is
                              also being changed to ExternalName (which requires this field to be
                              empty) or the type field is being changed from ExternalName (in which
                              case this field may optionally be specified, as describe above).  Valid
                              values are "None", empty string (""), or a valid IP address.  Setting
                              this to "None" makes a "headless service" (no virtual IP), which is
                              useful when direct endpoint connections are preferred and proxying is
                              not required.  Only applies to types ClusterIP, NodePort, and
                              LoadBalancer. If this field is specified when creating a Service of type
                              ExternalName, creation will fail. This field will be wiped when updating
                              a Service to type ExternalName.  If this field is not specified, it will
                              be initialized from the clusterIP field.  If this field is specified,
                              clients must ensure that clusterIPs[0] and clusterIP have the same
                              value.

                              This field may hold a maximum of two entries (dual-stack IPs, in either order).
                              These IPs must correspond to the values of the ipFamilies field. Both
                              clusterIPs and ipFamilies are governed by the ipFamilyPolicy field.
                              More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
                            items:
                              type: string
                            type: array
                            x-kubernetes-list-type: atomic
                          externalIPs:
                            description: |-
                              externalIPs is a list of IP addresses for which nodes in the cluster
                              will also accept traffic for this service.  These IPs are not managed by
                              Kubernetes.  The user is responsible for ensuring that traffic arrives
                              at a node with this IP.  A common example is external load-balancers
                              that are not part of the Kubernetes system.
                            items:
                              type: string
                            type: array
                            x-kubernetes-list-type: atomic
                          externalName:
                            description: |-
                              externalName is the external reference that discovery mechanisms will
                              return as an alias for this service (e.g. a DNS CNAME record). No
                              proxying will be involved.  Must be a lowercase RFC-1123 hostname
                              (https://tools.ietf.org/html/rfc1123) and requires `type` to be "ExternalName".
                            type: string
                          externalTrafficPolicy:
                            description: |-
                              externalTrafficPolicy describes how nodes distribute service traffic they
                              receive on one of the Service's "externally-facing" addresses (NodePorts,
                              ExternalIPs, and LoadBalancer IPs). If set to "Local", the proxy will configure
                              the service in a way that assumes that external load balancers will take care
                              of balancing the service traffic between nodes, and so each node will deliver
                              traffic only to the node-local endpoints of the service, without masquerading
                              the client source IP. (Traffic mistakenly sent to a node with no endpoints will
                              be dropped.) The default value, "Cluster", uses the standard behavior of
                              routing to all endpoints evenly (possibly modified by topology and other
                              features). Note that traffic sent to an External IP or LoadBalancer IP from
                              within the cluster will always get "Cluster" semantics, but clients sending to
                              a NodePort from within the cluster may need to take traffic policy into account
                              when picking a node.
                            type: string
                          healthCheckNodePort:
                            description: |-
                              healthCheckNodePort specifies the healthcheck nodePort for the service.
                              This only applies when type is set to LoadBalancer and
                              externalTrafficPolicy is set to Local. If a value is specified, is
                              in-range, and is not in use, it will be used.  If not specified, a value
                              will be automatically allocated.  External systems (e.g. load-balancers)
                              can use this port to determine if a given node holds endpoints for this
                              service or not.  If this field is specified when creating a Service
                              which does not need it, creation will fail. This field will be wiped
                              when updating a Service to no longer need it (e.g. changing type).
                              This field cannot be updated once set.
                            format: int32
                            type: integer
                          internalTrafficPolicy:
                            description: |-
                              InternalTrafficPolicy describes how nodes distribute service traffic they
                              receive on the ClusterIP. If set to "Local", the proxy will assume that pods
                              only want to talk to endpoints of the service on the same node as the pod,
                              dropping the traffic if there are no local endpoints. The default value,
                              "Cluster", uses the standard behavior of routing to all endpoints evenly
                              (possibly modified by topology and other features).
                            type: string
                          ipFamilies:
                            description: |-
                              IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this
                              service. This field is usually assigned automatically based on cluster
                              configuration and the ipFamilyPolicy field. If this field is specified
                              manually, the requested family is available in the cluster,
                              and ipFamilyPolicy allows it, it will be used; otherwise creation of
                              the service will fail. This field is conditionally mutable: it allows
                              for adding or removing a secondary IP family, but it does not allow
                              changing the primary IP family of the Service. Valid values are "IPv4"
                              and "IPv6".  This field only applies to Services of types ClusterIP,
                              NodePort, and LoadBalancer, and does apply to "headless" services.
                              This field will be wiped when updating a Service to type ExternalName.

                              This field may hold a maximum of two entries (dual-stack families, in
                              either order).  These families must correspond to the values of the
                              clusterIPs field, if specified. Both clusterIPs and ipFamilies are
                              governed by the ipFamilyPolicy field.
                            items:
                              description: |-
                                IPFamily represents the IP Family (IPv4 or IPv6). This type is used
                                to express the family of an IP expressed by a type (e.g. service.spec.ipFamilies).
                              type: string
                            type: array
                            x-kubernetes-list-type: atomic
                          ipFamilyPolicy:
                            description: |-
                              IPFamilyPolicy represents the dual-stack-ness requested or required by
                              this Service. If there is no value provided, then this field will be set
                              to SingleStack. Services can be "SingleStack" (a single IP family),
                              "PreferDualStack" (two IP families on dual-stack configured clusters or
                              a single IP family on single-stack clusters), or "RequireDualStack"
                              (two IP families on dual-stack configured clusters, otherwise fail). The
                              ipFamilies and clusterIPs fields depend on the value of this field. This
                              field will be wiped when updating a service to type ExternalName.
                            type: string
                          loadBalancerClass:
                            description: |-
                              loadBalancerClass is the class of the load balancer implementation this Service belongs to.
                              If specified, the value of this field must be a label-style identifier, with an optional prefix,
                              e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users.
                              This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load
                              balancer implementation is used, today this is typically done through the cloud provider integration,
                              but should apply for any default implementation. If set, it is assumed that a load balancer
                              implementation is watching for Services with a matching class. Any default load balancer
                              implementation (e.g. cloud providers) should ignore Services that set this field.
                              This field can only be set when creating or updating a Service to type 'LoadBalancer'.
                              Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type.
                            type: string
                          loadBalancerIP:
                            description: |-
                              Only applies to Service Type: LoadBalancer.
                              This feature depends on whether the underlying cloud-provider supports specifying
                              the loadBalancerIP when a load balancer is created.
                              This field will be ignored if the cloud-provider does not support the feature.
                              Deprecated: This field was under-specified and its meaning varies across implementations.
                              Using it is non-portable and it may not support dual-stack.
                              Users are encouraged to use implementation-specific annotations when available.
                            type: string
                          loadBalancerSourceRanges:
                            description: |-
                              If specified and supported by the platform, this will restrict traffic through the cloud-provider
                              load-balancer will be restricted to the specified client IPs. This field will be ignored if the
                              cloud-provider does not support the feature."
                              More info: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/
                            items:
                              type: string
                            type: array
                            x-kubernetes-list-type: atomic
                          ports:
                            description: |-
                              The list of ports that are exposed by this service.
                              More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
                            items:
                              description: ServicePort contains information on service's
                                port.
                              properties:
                                appProtocol:
                                  description: |-
                                    The application protocol for this port.
                                    This is used as a hint for implementations to offer richer behavior for protocols that they understand.
                                    This field follows standard Kubernetes label syntax.
                                    Valid values are either:

                                    * Un-prefixed protocol names - reserved for IANA standard service names (as per
                                    RFC-6335 and https://www.iana.org/assignments/service-names).

                                    * Kubernetes-defined prefixed names:
                                      * 'kubernetes.io/h2c' - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior-
                                      * 'kubernetes.io/ws'  - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
                                      * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455

                                    * Other protocols should use implementation-defined prefixed names such as
                                    mycompany.com/my-custom-protocol.
                                  type: string
                                name:
                                  description: |-
                                    The name of this port within the service. This must be a DNS_LABEL.
                                    All ports within a ServiceSpec must have unique names. When considering
                                    the endpoints for a Service, this must match the 'name' field in the
                                    EndpointPort.
                                    Optional if only one ServicePort is defined on this service.
                                  type: string
                                nodePort:
                                  description: |-
                                    The port on each node on which this service is exposed when type is
                                    NodePort or LoadBalancer.  Usually assigned by the system. If a value is
                                    specified, in-range, and not in use it will be used, otherwise the
                                    operation will fail.  If not specified, a port will be allocated if this
                                    Service requires one.  If this field is specified when creating a
                                    Service which does not need it, creation will fail. This field will be
                                    wiped when updating a Service to no longer need it (e.g. changing type
                                    from NodePort to ClusterIP).
                                    More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
                                  format: int32
                                  type: integer
                                port:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



