/**
 * This file was auto-generated by openapi-typescript.
 * Do not make direct changes to the file.
 */

export interface paths {
    "/api/system/controllers/config": {
        parameters: {
            query?: never;
            header?: never;
            path?: never;
            cookie?: never;
        };
        /**
         * Get server-wide controllers configuration defaults
         * @description Returns the server-wide default configuration for Meshery Operator, MeshSync, and Meshery Broker. These defaults apply to every managed Kubernetes connection that does not override them. Fields that have never been set are absent, meaning the built-in defaults apply.
         */
        get: operations["getControllersDefaultConfig"];
        /**
         * Update server-wide controllers configuration defaults
         * @description Persists the server-wide default configuration for Meshery Operator, MeshSync, and Meshery Broker, then re-applies the effective configuration to every connected Kubernetes connection that inherits the changed fields. Absent fields fall back to built-in defaults.
         */
        put: operations["updateControllersDefaultConfig"];
        post?: never;
        delete?: never;
        options?: never;
        head?: never;
        patch?: never;
        trace?: never;
    };
    "/api/integrations/connections/{connectionId}/controllers/config": {
        parameters: {
            query?: never;
            header?: never;
            path?: never;
            cookie?: never;
        };
        /**
         * Get controllers configuration for a connection
         * @description Returns the controllers configuration for a single Kubernetes connection at every layer: the per-connection override stored on the connection, the current server-wide default, and the resolved effective configuration (override, then server default, then built-in default).
         */
        get: operations["getConnectionControllersConfig"];
        /**
         * Update controllers configuration override for a connection
         * @description Persists the per-connection controllers configuration override into the connection's metadata and applies the resolved effective configuration to that connection's cluster. Absent fields inherit the server-wide default; an empty document removes the override entirely.
         */
        put: operations["updateConnectionControllersConfig"];
        post?: never;
        delete?: never;
        options?: never;
        head?: never;
        patch?: never;
        trace?: never;
    };
}
export type webhooks = Record<string, never>;
export interface components {
    schemas: {
        /**
         * MesheryControllersConfig
         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
         */
        MesheryControllersConfig: {
            /**
             * @description Specifies the version of the schema used for this configuration document.
             * @default controllers.meshery.io/v1alpha1
             * @example [
             *       "v1",
             *       "v1alpha1",
             *       "v2beta3",
             *       "v1.custom-suffix",
             *       "models.meshery.io/v1beta1",
             *       "capability.meshery.io/v1alpha1"
             *     ]
             */
            schemaVersion: string;
            /** @description Configuration for the Meshery Operator on the managed cluster. */
            operator?: {
                /**
                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                 * @enum {string}
                 */
                deploymentMode?: "operator" | "embedded";
                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                version?: string;
            };
            /** @description Configuration for the MeshSync agent on the managed cluster. */
            meshsync?: {
                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                version?: string;
                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                replicas?: number;
                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                watchList?: {
                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                    whitelist?: {
                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                        resource: string;
                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                    }[];
                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                    blacklist?: string[];
                };
                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                outputNamespaces?: string[];
                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                outputResources?: string[];
                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                redactSecrets?: boolean;
                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                brokerContentDedup?: boolean;
                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                debugLogging?: boolean;
            };
            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
            broker?: {
                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                version?: string;
                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                replicas?: number;
                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                service?: {
                    /**
                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                     * @enum {string}
                     */
                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                    annotations?: {
                        [key: string]: string;
                    };
                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                    loadBalancerClass?: string;
                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                    loadBalancerSourceRanges?: string[];
                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                    externalEndpointOverride?: string;
                };
            };
        };
        /** @description Layered view of the controllers configuration for a single Kubernetes connection. Exposes each precedence layer so clients can indicate, per field, whether the effective value is inherited from the server-wide default or overridden on the connection. */
        ConnectionControllersConfig: {
            /**
             * MesheryControllersConfig
             * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
             */
            override?: {
                /**
                 * @description Specifies the version of the schema used for this configuration document.
                 * @default controllers.meshery.io/v1alpha1
                 * @example [
                 *       "v1",
                 *       "v1alpha1",
                 *       "v2beta3",
                 *       "v1.custom-suffix",
                 *       "models.meshery.io/v1beta1",
                 *       "capability.meshery.io/v1alpha1"
                 *     ]
                 */
                schemaVersion: string;
                /** @description Configuration for the Meshery Operator on the managed cluster. */
                operator?: {
                    /**
                     * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                     * @enum {string}
                     */
                    deploymentMode?: "operator" | "embedded";
                    /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                    version?: string;
                };
                /** @description Configuration for the MeshSync agent on the managed cluster. */
                meshsync?: {
                    /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                    version?: string;
                    /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                    replicas?: number;
                    /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                    watchList?: {
                        /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                        whitelist?: {
                            /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                            resource: string;
                            /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                            events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                        }[];
                        /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                        blacklist?: string[];
                    };
                    /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                    outputNamespaces?: string[];
                    /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                    outputResources?: string[];
                    /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                    redactSecrets?: boolean;
                    /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                    brokerContentDedup?: boolean;
                    /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                    debugLogging?: boolean;
                };
                /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                broker?: {
                    /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                    version?: string;
                    /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                    replicas?: number;
                    /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                    service?: {
                        /**
                         * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                         * @enum {string}
                         */
                        type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                        /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                        annotations?: {
                            [key: string]: string;
                        };
                        /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                        loadBalancerClass?: string;
                        /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                        loadBalancerSourceRanges?: string[];
                        /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                        externalEndpointOverride?: string;
                    };
                };
            };
            /**
             * MesheryControllersConfig
             * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
             */
            default?: {
                /**
                 * @description Specifies the version of the schema used for this configuration document.
                 * @default controllers.meshery.io/v1alpha1
                 * @example [
                 *       "v1",
                 *       "v1alpha1",
                 *       "v2beta3",
                 *       "v1.custom-suffix",
                 *       "models.meshery.io/v1beta1",
                 *       "capability.meshery.io/v1alpha1"
                 *     ]
                 */
                schemaVersion: string;
                /** @description Configuration for the Meshery Operator on the managed cluster. */
                operator?: {
                    /**
                     * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                     * @enum {string}
                     */
                    deploymentMode?: "operator" | "embedded";
                    /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                    version?: string;
                };
                /** @description Configuration for the MeshSync agent on the managed cluster. */
                meshsync?: {
                    /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                    version?: string;
                    /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                    replicas?: number;
                    /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                    watchList?: {
                        /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                        whitelist?: {
                            /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                            resource: string;
                            /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                            events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                        }[];
                        /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                        blacklist?: string[];
                    };
                    /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                    outputNamespaces?: string[];
                    /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                    outputResources?: string[];
                    /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                    redactSecrets?: boolean;
                    /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                    brokerContentDedup?: boolean;
                    /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                    debugLogging?: boolean;
                };
                /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                broker?: {
                    /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                    version?: string;
                    /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                    replicas?: number;
                    /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                    service?: {
                        /**
                         * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                         * @enum {string}
                         */
                        type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                        /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                        annotations?: {
                            [key: string]: string;
                        };
                        /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                        loadBalancerClass?: string;
                        /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                        loadBalancerSourceRanges?: string[];
                        /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                        externalEndpointOverride?: string;
                    };
                };
            };
            /**
             * MesheryControllersConfig
             * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
             */
            effective: {
                /**
                 * @description Specifies the version of the schema used for this configuration document.
                 * @default controllers.meshery.io/v1alpha1
                 * @example [
                 *       "v1",
                 *       "v1alpha1",
                 *       "v2beta3",
                 *       "v1.custom-suffix",
                 *       "models.meshery.io/v1beta1",
                 *       "capability.meshery.io/v1alpha1"
                 *     ]
                 */
                schemaVersion: string;
                /** @description Configuration for the Meshery Operator on the managed cluster. */
                operator?: {
                    /**
                     * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                     * @enum {string}
                     */
                    deploymentMode?: "operator" | "embedded";
                    /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                    version?: string;
                };
                /** @description Configuration for the MeshSync agent on the managed cluster. */
                meshsync?: {
                    /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                    version?: string;
                    /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                    replicas?: number;
                    /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                    watchList?: {
                        /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                        whitelist?: {
                            /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                            resource: string;
                            /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                            events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                        }[];
                        /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                        blacklist?: string[];
                    };
                    /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                    outputNamespaces?: string[];
                    /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                    outputResources?: string[];
                    /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                    redactSecrets?: boolean;
                    /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                    brokerContentDedup?: boolean;
                    /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                    debugLogging?: boolean;
                };
                /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                broker?: {
                    /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                    version?: string;
                    /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                    replicas?: number;
                    /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                    service?: {
                        /**
                         * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                         * @enum {string}
                         */
                        type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                        /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                        annotations?: {
                            [key: string]: string;
                        };
                        /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                        loadBalancerClass?: string;
                        /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                        loadBalancerSourceRanges?: string[];
                        /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                        externalEndpointOverride?: string;
                    };
                };
            };
        };
        /** @description Client-settable controllers configuration document, used as the body of update requests at both layers (server-wide defaults and per-connection override). Identical to MesheryControllersConfig minus the server-stamped schemaVersion. Every field is optional: an absent field inherits from the next precedence layer, and an empty document clears the layer entirely. */
        MesheryControllersConfigPayload: {
            /** @description Configuration for the Meshery Operator on the managed cluster. */
            operator?: {
                /**
                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                 * @enum {string}
                 */
                deploymentMode?: "operator" | "embedded";
                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                version?: string;
            };
            /** @description Configuration for the MeshSync agent on the managed cluster. */
            meshsync?: {
                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                version?: string;
                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                replicas?: number;
                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                watchList?: {
                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                    whitelist?: {
                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                        resource: string;
                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                    }[];
                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                    blacklist?: string[];
                };
                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                outputNamespaces?: string[];
                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                outputResources?: string[];
                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                redactSecrets?: boolean;
                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                brokerContentDedup?: boolean;
                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                debugLogging?: boolean;
            };
            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
            broker?: {
                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                version?: string;
                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                replicas?: number;
                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                service?: {
                    /**
                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                     * @enum {string}
                     */
                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                    annotations?: {
                        [key: string]: string;
                    };
                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                    loadBalancerClass?: string;
                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                    loadBalancerSourceRanges?: string[];
                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                    externalEndpointOverride?: string;
                };
            };
        };
        /** @description Configuration for the Meshery Operator on a managed cluster. The operator deploys and reconciles MeshSync and Meshery Broker; in embedded mode no operator is installed and MeshSync runs in-process inside Meshery Server. */
        MesheryOperatorConfig: {
            /**
             * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
             * @enum {string}
             */
            deploymentMode?: "operator" | "embedded";
            /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
            version?: string;
        };
        /** @description Configuration for the MeshSync agent that discovers and synchronizes cluster state. In operator deployment mode these settings are applied through the MeshSync custom resource and the MeshSync Deployment on the managed cluster; in embedded mode the applicable settings are passed to the in-process MeshSync run. */
        MeshSyncConfig: {
            /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
            version?: string;
            /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
            replicas?: number;
            /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
            watchList?: {
                /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                whitelist?: {
                    /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                    resource: string;
                    /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                    events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                }[];
                /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                blacklist?: string[];
            };
            /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
            outputNamespaces?: string[];
            /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
            outputResources?: string[];
            /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
            redactSecrets?: boolean;
            /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
            brokerContentDedup?: boolean;
            /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
            debugLogging?: boolean;
        };
        /** @description Discovery scope for MeshSync. At most one of whitelist or blacklist may be set (enforced by this schema and by MeshSync itself): a whitelist watches only the listed resource types with the listed event types, while a blacklist watches MeshSync's default resource set minus the listed resource types. When both are empty or absent, MeshSync watches its built-in default resource set. Applied through the MeshSync custom resource; MeshSync reads it at startup, so changes trigger a MeshSync restart. */
        MeshSyncWatchList: {
            /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
            whitelist?: {
                /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                resource: string;
                /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                events?: ("ADDED" | "MODIFIED" | "DELETED")[];
            }[];
            /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
            blacklist?: string[];
        };
        /** @description A single watched Kubernetes resource type and the event types MeshSync subscribes to for it. */
        MeshSyncWatchedResource: {
            /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
            resource: string;
            /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
            events?: ("ADDED" | "MODIFIED" | "DELETED")[];
        };
        /** @description Configuration for the Meshery Broker (NATS) that MeshSync publishes to. Applies to operator deployment mode only: the settings are applied through the Broker custom resource on the managed cluster. In embedded mode no broker is installed; MeshSync publishes over an in-process channel inside Meshery Server. */
        MesheryBrokerConfig: {
            /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
            version?: string;
            /** @description Number of NATS server replicas (Broker custom resource spec.size). */
            replicas?: number;
            /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
            service?: {
                /**
                 * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                 * @enum {string}
                 */
                type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                annotations?: {
                    [key: string]: string;
                };
                /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                loadBalancerClass?: string;
                /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                loadBalancerSourceRanges?: string[];
                /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                externalEndpointOverride?: string;
            };
        };
        /** @description Networking configuration for the broker's client-facing Kubernetes Service (Broker custom resource spec.service). Every field reconciles in place: the operator updates the live Service and re-derives the broker endpoint without recreating broker pods. */
        MesheryBrokerServiceConfig: {
            /**
             * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
             * @enum {string}
             */
            type?: "ClusterIP" | "NodePort" | "LoadBalancer";
            /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
            annotations?: {
                [key: string]: string;
            };
            /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
            loadBalancerClass?: string;
            /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
            loadBalancerSourceRanges?: string[];
            /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
            externalEndpointOverride?: string;
        };
    };
    responses: {
        /** @description Invalid request body or request param */
        400: {
            headers: {
                [name: string]: unknown;
            };
            content: {
                "text/plain": string;
            };
        };
        /** @description Expired JWT token used or insufficient privilege */
        401: {
            headers: {
                [name: string]: unknown;
            };
            content: {
                "text/plain": string;
            };
        };
        /** @description Result not found */
        404: {
            headers: {
                [name: string]: unknown;
            };
            content: {
                "text/plain": string;
            };
        };
        /** @description Internal server error */
        500: {
            headers: {
                [name: string]: unknown;
            };
            content: {
                "text/plain": string;
            };
        };
    };
    parameters: {
        /** @description Kubernetes connection ID. */
        connectionId: string;
    };
    requestBodies: {
        /** @description Controllers configuration document. Absent fields inherit from the next precedence layer. */
        controllersConfigPayload: {
            content: {
                "application/json": {
                    /** @description Configuration for the Meshery Operator on the managed cluster. */
                    operator?: {
                        /**
                         * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                         * @enum {string}
                         */
                        deploymentMode?: "operator" | "embedded";
                        /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                        version?: string;
                    };
                    /** @description Configuration for the MeshSync agent on the managed cluster. */
                    meshsync?: {
                        /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                        version?: string;
                        /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                        replicas?: number;
                        /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                        watchList?: {
                            /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                            whitelist?: {
                                /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                resource: string;
                                /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                            }[];
                            /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                            blacklist?: string[];
                        };
                        /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                        outputNamespaces?: string[];
                        /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                        outputResources?: string[];
                        /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                        redactSecrets?: boolean;
                        /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                        brokerContentDedup?: boolean;
                        /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                        debugLogging?: boolean;
                    };
                    /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                    broker?: {
                        /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                        version?: string;
                        /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                        replicas?: number;
                        /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                        service?: {
                            /**
                             * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                             * @enum {string}
                             */
                            type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                            /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                            annotations?: {
                                [key: string]: string;
                            };
                            /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                            loadBalancerClass?: string;
                            /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                            loadBalancerSourceRanges?: string[];
                            /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                            externalEndpointOverride?: string;
                        };
                    };
                };
            };
        };
    };
    headers: never;
    pathItems: never;
}
export type $defs = Record<string, never>;
export interface operations {
    getControllersDefaultConfig: {
        parameters: {
            query?: never;
            header?: never;
            path?: never;
            cookie?: never;
        };
        requestBody?: never;
        responses: {
            /** @description Server-wide controllers configuration defaults */
            200: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "application/json": {
                        /**
                         * @description Specifies the version of the schema used for this configuration document.
                         * @default controllers.meshery.io/v1alpha1
                         * @example [
                         *       "v1",
                         *       "v1alpha1",
                         *       "v2beta3",
                         *       "v1.custom-suffix",
                         *       "models.meshery.io/v1beta1",
                         *       "capability.meshery.io/v1alpha1"
                         *     ]
                         */
                        schemaVersion: string;
                        /** @description Configuration for the Meshery Operator on the managed cluster. */
                        operator?: {
                            /**
                             * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                             * @enum {string}
                             */
                            deploymentMode?: "operator" | "embedded";
                            /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                            version?: string;
                        };
                        /** @description Configuration for the MeshSync agent on the managed cluster. */
                        meshsync?: {
                            /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                            version?: string;
                            /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                            replicas?: number;
                            /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                            watchList?: {
                                /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                whitelist?: {
                                    /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                    resource: string;
                                    /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                    events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                }[];
                                /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                blacklist?: string[];
                            };
                            /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                            outputNamespaces?: string[];
                            /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                            outputResources?: string[];
                            /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                            redactSecrets?: boolean;
                            /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                            brokerContentDedup?: boolean;
                            /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                            debugLogging?: boolean;
                        };
                        /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                        broker?: {
                            /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                            version?: string;
                            /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                            replicas?: number;
                            /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                            service?: {
                                /**
                                 * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                 * @enum {string}
                                 */
                                type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                annotations?: {
                                    [key: string]: string;
                                };
                                /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                loadBalancerClass?: string;
                                /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                loadBalancerSourceRanges?: string[];
                                /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                externalEndpointOverride?: string;
                            };
                        };
                    };
                };
            };
            /** @description Expired JWT token used or insufficient privilege */
            401: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Internal server error */
            500: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
        };
    };
    updateControllersDefaultConfig: {
        parameters: {
            query?: never;
            header?: never;
            path?: never;
            cookie?: never;
        };
        /** @description Controllers configuration document. Absent fields inherit from the next precedence layer. */
        requestBody: {
            content: {
                "application/json": {
                    /** @description Configuration for the Meshery Operator on the managed cluster. */
                    operator?: {
                        /**
                         * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                         * @enum {string}
                         */
                        deploymentMode?: "operator" | "embedded";
                        /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                        version?: string;
                    };
                    /** @description Configuration for the MeshSync agent on the managed cluster. */
                    meshsync?: {
                        /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                        version?: string;
                        /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                        replicas?: number;
                        /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                        watchList?: {
                            /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                            whitelist?: {
                                /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                resource: string;
                                /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                            }[];
                            /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                            blacklist?: string[];
                        };
                        /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                        outputNamespaces?: string[];
                        /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                        outputResources?: string[];
                        /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                        redactSecrets?: boolean;
                        /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                        brokerContentDedup?: boolean;
                        /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                        debugLogging?: boolean;
                    };
                    /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                    broker?: {
                        /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                        version?: string;
                        /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                        replicas?: number;
                        /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                        service?: {
                            /**
                             * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                             * @enum {string}
                             */
                            type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                            /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                            annotations?: {
                                [key: string]: string;
                            };
                            /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                            loadBalancerClass?: string;
                            /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                            loadBalancerSourceRanges?: string[];
                            /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                            externalEndpointOverride?: string;
                        };
                    };
                };
            };
        };
        responses: {
            /** @description Persisted server-wide controllers configuration defaults */
            200: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "application/json": {
                        /**
                         * @description Specifies the version of the schema used for this configuration document.
                         * @default controllers.meshery.io/v1alpha1
                         * @example [
                         *       "v1",
                         *       "v1alpha1",
                         *       "v2beta3",
                         *       "v1.custom-suffix",
                         *       "models.meshery.io/v1beta1",
                         *       "capability.meshery.io/v1alpha1"
                         *     ]
                         */
                        schemaVersion: string;
                        /** @description Configuration for the Meshery Operator on the managed cluster. */
                        operator?: {
                            /**
                             * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                             * @enum {string}
                             */
                            deploymentMode?: "operator" | "embedded";
                            /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                            version?: string;
                        };
                        /** @description Configuration for the MeshSync agent on the managed cluster. */
                        meshsync?: {
                            /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                            version?: string;
                            /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                            replicas?: number;
                            /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                            watchList?: {
                                /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                whitelist?: {
                                    /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                    resource: string;
                                    /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                    events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                }[];
                                /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                blacklist?: string[];
                            };
                            /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                            outputNamespaces?: string[];
                            /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                            outputResources?: string[];
                            /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                            redactSecrets?: boolean;
                            /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                            brokerContentDedup?: boolean;
                            /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                            debugLogging?: boolean;
                        };
                        /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                        broker?: {
                            /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                            version?: string;
                            /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                            replicas?: number;
                            /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                            service?: {
                                /**
                                 * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                 * @enum {string}
                                 */
                                type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                annotations?: {
                                    [key: string]: string;
                                };
                                /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                loadBalancerClass?: string;
                                /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                loadBalancerSourceRanges?: string[];
                                /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                externalEndpointOverride?: string;
                            };
                        };
                    };
                };
            };
            /** @description Invalid request body or request param */
            400: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Expired JWT token used or insufficient privilege */
            401: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Internal server error */
            500: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
        };
    };
    getConnectionControllersConfig: {
        parameters: {
            query?: never;
            header?: never;
            path: {
                /** @description Kubernetes connection ID. */
                connectionId: string;
            };
            cookie?: never;
        };
        requestBody?: never;
        responses: {
            /** @description Controllers configuration for the connection */
            200: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "application/json": {
                        /**
                         * MesheryControllersConfig
                         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
                         */
                        override?: {
                            /**
                             * @description Specifies the version of the schema used for this configuration document.
                             * @default controllers.meshery.io/v1alpha1
                             * @example [
                             *       "v1",
                             *       "v1alpha1",
                             *       "v2beta3",
                             *       "v1.custom-suffix",
                             *       "models.meshery.io/v1beta1",
                             *       "capability.meshery.io/v1alpha1"
                             *     ]
                             */
                            schemaVersion: string;
                            /** @description Configuration for the Meshery Operator on the managed cluster. */
                            operator?: {
                                /**
                                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                                 * @enum {string}
                                 */
                                deploymentMode?: "operator" | "embedded";
                                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                                version?: string;
                            };
                            /** @description Configuration for the MeshSync agent on the managed cluster. */
                            meshsync?: {
                                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                                version?: string;
                                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                                replicas?: number;
                                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                                watchList?: {
                                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                    whitelist?: {
                                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                        resource: string;
                                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                    }[];
                                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                    blacklist?: string[];
                                };
                                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                                outputNamespaces?: string[];
                                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                                outputResources?: string[];
                                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                                redactSecrets?: boolean;
                                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                                brokerContentDedup?: boolean;
                                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                                debugLogging?: boolean;
                            };
                            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                            broker?: {
                                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                                version?: string;
                                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                                replicas?: number;
                                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                                service?: {
                                    /**
                                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                     * @enum {string}
                                     */
                                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                    annotations?: {
                                        [key: string]: string;
                                    };
                                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                    loadBalancerClass?: string;
                                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                    loadBalancerSourceRanges?: string[];
                                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                    externalEndpointOverride?: string;
                                };
                            };
                        };
                        /**
                         * MesheryControllersConfig
                         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
                         */
                        default?: {
                            /**
                             * @description Specifies the version of the schema used for this configuration document.
                             * @default controllers.meshery.io/v1alpha1
                             * @example [
                             *       "v1",
                             *       "v1alpha1",
                             *       "v2beta3",
                             *       "v1.custom-suffix",
                             *       "models.meshery.io/v1beta1",
                             *       "capability.meshery.io/v1alpha1"
                             *     ]
                             */
                            schemaVersion: string;
                            /** @description Configuration for the Meshery Operator on the managed cluster. */
                            operator?: {
                                /**
                                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                                 * @enum {string}
                                 */
                                deploymentMode?: "operator" | "embedded";
                                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                                version?: string;
                            };
                            /** @description Configuration for the MeshSync agent on the managed cluster. */
                            meshsync?: {
                                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                                version?: string;
                                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                                replicas?: number;
                                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                                watchList?: {
                                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                    whitelist?: {
                                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                        resource: string;
                                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                    }[];
                                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                    blacklist?: string[];
                                };
                                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                                outputNamespaces?: string[];
                                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                                outputResources?: string[];
                                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                                redactSecrets?: boolean;
                                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                                brokerContentDedup?: boolean;
                                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                                debugLogging?: boolean;
                            };
                            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                            broker?: {
                                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                                version?: string;
                                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                                replicas?: number;
                                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                                service?: {
                                    /**
                                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                     * @enum {string}
                                     */
                                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                    annotations?: {
                                        [key: string]: string;
                                    };
                                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                    loadBalancerClass?: string;
                                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                    loadBalancerSourceRanges?: string[];
                                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                    externalEndpointOverride?: string;
                                };
                            };
                        };
                        /**
                         * MesheryControllersConfig
                         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
                         */
                        effective: {
                            /**
                             * @description Specifies the version of the schema used for this configuration document.
                             * @default controllers.meshery.io/v1alpha1
                             * @example [
                             *       "v1",
                             *       "v1alpha1",
                             *       "v2beta3",
                             *       "v1.custom-suffix",
                             *       "models.meshery.io/v1beta1",
                             *       "capability.meshery.io/v1alpha1"
                             *     ]
                             */
                            schemaVersion: string;
                            /** @description Configuration for the Meshery Operator on the managed cluster. */
                            operator?: {
                                /**
                                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                                 * @enum {string}
                                 */
                                deploymentMode?: "operator" | "embedded";
                                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                                version?: string;
                            };
                            /** @description Configuration for the MeshSync agent on the managed cluster. */
                            meshsync?: {
                                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                                version?: string;
                                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                                replicas?: number;
                                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                                watchList?: {
                                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                    whitelist?: {
                                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                        resource: string;
                                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                    }[];
                                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                    blacklist?: string[];
                                };
                                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                                outputNamespaces?: string[];
                                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                                outputResources?: string[];
                                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                                redactSecrets?: boolean;
                                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                                brokerContentDedup?: boolean;
                                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                                debugLogging?: boolean;
                            };
                            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                            broker?: {
                                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                                version?: string;
                                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                                replicas?: number;
                                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                                service?: {
                                    /**
                                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                     * @enum {string}
                                     */
                                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                    annotations?: {
                                        [key: string]: string;
                                    };
                                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                    loadBalancerClass?: string;
                                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                    loadBalancerSourceRanges?: string[];
                                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                    externalEndpointOverride?: string;
                                };
                            };
                        };
                    };
                };
            };
            /** @description Invalid request body or request param */
            400: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Expired JWT token used or insufficient privilege */
            401: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Result not found */
            404: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Internal server error */
            500: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
        };
    };
    updateConnectionControllersConfig: {
        parameters: {
            query?: never;
            header?: never;
            path: {
                /** @description Kubernetes connection ID. */
                connectionId: string;
            };
            cookie?: never;
        };
        /** @description Controllers configuration document. Absent fields inherit from the next precedence layer. */
        requestBody: {
            content: {
                "application/json": {
                    /** @description Configuration for the Meshery Operator on the managed cluster. */
                    operator?: {
                        /**
                         * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                         * @enum {string}
                         */
                        deploymentMode?: "operator" | "embedded";
                        /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                        version?: string;
                    };
                    /** @description Configuration for the MeshSync agent on the managed cluster. */
                    meshsync?: {
                        /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                        version?: string;
                        /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                        replicas?: number;
                        /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                        watchList?: {
                            /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                            whitelist?: {
                                /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                resource: string;
                                /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                            }[];
                            /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                            blacklist?: string[];
                        };
                        /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                        outputNamespaces?: string[];
                        /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                        outputResources?: string[];
                        /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                        redactSecrets?: boolean;
                        /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                        brokerContentDedup?: boolean;
                        /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                        debugLogging?: boolean;
                    };
                    /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                    broker?: {
                        /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                        version?: string;
                        /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                        replicas?: number;
                        /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                        service?: {
                            /**
                             * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                             * @enum {string}
                             */
                            type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                            /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                            annotations?: {
                                [key: string]: string;
                            };
                            /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                            loadBalancerClass?: string;
                            /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                            loadBalancerSourceRanges?: string[];
                            /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                            externalEndpointOverride?: string;
                        };
                    };
                };
            };
        };
        responses: {
            /** @description Updated controllers configuration for the connection */
            200: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "application/json": {
                        /**
                         * MesheryControllersConfig
                         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
                         */
                        override?: {
                            /**
                             * @description Specifies the version of the schema used for this configuration document.
                             * @default controllers.meshery.io/v1alpha1
                             * @example [
                             *       "v1",
                             *       "v1alpha1",
                             *       "v2beta3",
                             *       "v1.custom-suffix",
                             *       "models.meshery.io/v1beta1",
                             *       "capability.meshery.io/v1alpha1"
                             *     ]
                             */
                            schemaVersion: string;
                            /** @description Configuration for the Meshery Operator on the managed cluster. */
                            operator?: {
                                /**
                                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                                 * @enum {string}
                                 */
                                deploymentMode?: "operator" | "embedded";
                                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                                version?: string;
                            };
                            /** @description Configuration for the MeshSync agent on the managed cluster. */
                            meshsync?: {
                                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                                version?: string;
                                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                                replicas?: number;
                                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                                watchList?: {
                                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                    whitelist?: {
                                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                        resource: string;
                                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                    }[];
                                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                    blacklist?: string[];
                                };
                                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                                outputNamespaces?: string[];
                                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                                outputResources?: string[];
                                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                                redactSecrets?: boolean;
                                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                                brokerContentDedup?: boolean;
                                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                                debugLogging?: boolean;
                            };
                            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                            broker?: {
                                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                                version?: string;
                                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                                replicas?: number;
                                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                                service?: {
                                    /**
                                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                     * @enum {string}
                                     */
                                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                    annotations?: {
                                        [key: string]: string;
                                    };
                                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                    loadBalancerClass?: string;
                                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                    loadBalancerSourceRanges?: string[];
                                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                    externalEndpointOverride?: string;
                                };
                            };
                        };
                        /**
                         * MesheryControllersConfig
                         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
                         */
                        default?: {
                            /**
                             * @description Specifies the version of the schema used for this configuration document.
                             * @default controllers.meshery.io/v1alpha1
                             * @example [
                             *       "v1",
                             *       "v1alpha1",
                             *       "v2beta3",
                             *       "v1.custom-suffix",
                             *       "models.meshery.io/v1beta1",
                             *       "capability.meshery.io/v1alpha1"
                             *     ]
                             */
                            schemaVersion: string;
                            /** @description Configuration for the Meshery Operator on the managed cluster. */
                            operator?: {
                                /**
                                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                                 * @enum {string}
                                 */
                                deploymentMode?: "operator" | "embedded";
                                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                                version?: string;
                            };
                            /** @description Configuration for the MeshSync agent on the managed cluster. */
                            meshsync?: {
                                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                                version?: string;
                                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                                replicas?: number;
                                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                                watchList?: {
                                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                    whitelist?: {
                                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                        resource: string;
                                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                    }[];
                                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                    blacklist?: string[];
                                };
                                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                                outputNamespaces?: string[];
                                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                                outputResources?: string[];
                                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                                redactSecrets?: boolean;
                                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                                brokerContentDedup?: boolean;
                                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                                debugLogging?: boolean;
                            };
                            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                            broker?: {
                                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                                version?: string;
                                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                                replicas?: number;
                                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                                service?: {
                                    /**
                                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                     * @enum {string}
                                     */
                                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                    annotations?: {
                                        [key: string]: string;
                                    };
                                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                    loadBalancerClass?: string;
                                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                    loadBalancerSourceRanges?: string[];
                                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                    externalEndpointOverride?: string;
                                };
                            };
                        };
                        /**
                         * MesheryControllersConfig
                         * @description Deployment and runtime configuration for the Meshery controllers that manage a Kubernetes connection: Meshery Operator, MeshSync, and Meshery Broker. The same document shape is used at two layers. As a server-wide default it declares how Meshery Server deploys and configures the controllers for every managed cluster. As a per-connection override, stored in the connection's metadata, it overrides the server-wide default for a single connection. Every configuration field is optional: an absent field inherits the value from the next layer (per-connection override, then server-wide default, then built-in default). The only required field is the server-stamped schemaVersion discriminator, which identifies the document revision for future migrations. Learn more at https://docs.meshery.io/concepts/architecture
                         */
                        effective: {
                            /**
                             * @description Specifies the version of the schema used for this configuration document.
                             * @default controllers.meshery.io/v1alpha1
                             * @example [
                             *       "v1",
                             *       "v1alpha1",
                             *       "v2beta3",
                             *       "v1.custom-suffix",
                             *       "models.meshery.io/v1beta1",
                             *       "capability.meshery.io/v1alpha1"
                             *     ]
                             */
                            schemaVersion: string;
                            /** @description Configuration for the Meshery Operator on the managed cluster. */
                            operator?: {
                                /**
                                 * @description How MeshSync is deployed for the connection. "operator" installs Meshery Operator into the cluster, which runs MeshSync and Meshery Broker there; "embedded" runs MeshSync in-process inside Meshery Server and installs nothing into the cluster.
                                 * @enum {string}
                                 */
                                deploymentMode?: "operator" | "embedded";
                                /** @description Meshery Operator Helm chart version to deploy. When absent, the operator version tracks the Meshery Server release. */
                                version?: string;
                            };
                            /** @description Configuration for the MeshSync agent on the managed cluster. */
                            meshsync?: {
                                /** @description MeshSync image tag to run (for example "v1.0.2" or "stable-latest"). Applies to operator deployment mode only; in embedded mode MeshSync runs at the version compiled into Meshery Server. Secret redaction and broker content deduplication require MeshSync v1.0.2 or newer. */
                                version?: string;
                                /** @description Number of MeshSync replicas (MeshSync custom resource spec.size). Applies to operator deployment mode only. */
                                replicas?: number;
                                /** @description Discovery scope for MeshSync, as a whitelist or a blacklist of Kubernetes resource types. */
                                watchList?: {
                                    /** @description Resource types MeshSync watches, each with the event types to subscribe to. Mutually exclusive with blacklist. */
                                    whitelist?: {
                                        /** @description Resource key in "<plural>.<version>.<group>" form (for example "pods.v1." for core-group pods or "deployments.v1.apps"). */
                                        resource: string;
                                        /** @description Event types to subscribe to for this resource. Empty or absent subscribes to all event types. */
                                        events?: ("ADDED" | "MODIFIED" | "DELETED")[];
                                    }[];
                                    /** @description Resource types excluded from MeshSync's default discovery scope, in "<plural>.<version>.<group>" form (for example "pods.v1." or "deployments.v1.apps"). Mutually exclusive with whitelist. */
                                    blacklist?: string[];
                                };
                                /** @description Namespaces whose resources MeshSync publishes. Empty or absent publishes resources from all namespaces. Discovery scope is unaffected; this filters only what is published. */
                                outputNamespaces?: string[];
                                /** @description Resource types MeshSync publishes (lowercase Kubernetes kinds, for example "pod" or "deployment"). Empty or absent publishes all discovered resource types. Discovery scope is unaffected; this filters only what is published. */
                                outputResources?: string[];
                                /** @description When true, MeshSync redacts Kubernetes Secret data values (keys are preserved) before publishing. Requires MeshSync v1.0.2 or newer. Off by default; enabling is recommended when Secrets are within the discovery scope. */
                                redactSecrets?: boolean;
                                /** @description When true, MeshSync suppresses byte-identical republishes of a resource to the broker. Requires MeshSync v1.0.2 or newer. Off by default. */
                                brokerContentDedup?: boolean;
                                /** @description When true, MeshSync runs with debug-level logging (DEBUG environment variable). */
                                debugLogging?: boolean;
                            };
                            /** @description Configuration for the Meshery Broker (NATS) on the managed cluster. */
                            broker?: {
                                /** @description NATS server image tag to run (Broker custom resource spec.version). When absent, the operator's bundled default NATS version is used. */
                                version?: string;
                                /** @description Number of NATS server replicas (Broker custom resource spec.size). */
                                replicas?: number;
                                /** @description How the broker is exposed on the network. Service changes reconcile in place without restarting broker pods. */
                                service?: {
                                    /**
                                     * @description Kubernetes Service type for client access. When absent the broker stays cluster-internal (ClusterIP). LoadBalancer acquires a cloud load-balancer address; NodePort exposes the broker on node IPs.
                                     * @enum {string}
                                     */
                                    type?: "ClusterIP" | "NodePort" | "LoadBalancer";
                                    /** @description Annotations merged onto the client Service (cloud load-balancer hints, MetalLB address pools, internal-LB switches). */
                                    annotations?: {
                                        [key: string]: string;
                                    };
                                    /** @description Load-balancer implementation to use. Valid only when type is LoadBalancer. */
                                    loadBalancerClass?: string;
                                    /** @description CIDR ranges allowed to reach the broker. Valid only when type is LoadBalancer. */
                                    loadBalancerSourceRanges?: string[];
                                    /** @description Pins the advertised external broker endpoint as "host:port" when auto-derivation is undesirable: an ingress or gateway in front of the broker, an air-gapped topology, or NAT. The nats:// scheme is added by consumers. */
                                    externalEndpointOverride?: string;
                                };
                            };
                        };
                    };
                };
            };
            /** @description Invalid request body or request param */
            400: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Expired JWT token used or insufficient privilege */
            401: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Result not found */
            404: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
            /** @description Internal server error */
            500: {
                headers: {
                    [name: string]: unknown;
                };
                content: {
                    "text/plain": string;
                };
            };
        };
    };
}
