Alauda Service Mesh
  • Русский
    • Description
    ServiceMeshGroup is the Schema for the servicemeshgroups API
    Type
    object

    Specification

    PropertyTypeDescription
    apiVersionstring

    APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

    kindstring

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

    metadataObjectMeta

    ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.

    specobject

    ServiceMeshGroupSpec defines the desired state of ServiceMeshGroup

    statusobject

    ServiceMeshGroupStatus defines the observed state of ServiceMeshGroup

    .spec

    Description
    ServiceMeshGroupSpec defines the desired state of ServiceMeshGroup
    Type
    object
    Required
    primary
    PropertyTypeDescription
    caConfigobject
    clustersarray
    groupIDstring
    istioConfigobject
    istioVersionstring
    k8sVersionstring
    meshCommonConfigobject
    meshConfigobject
    multiClusterobject
    networkstring
    primarystring

    Deprecated: PrimaryCluster 仅做为主从结构的兼容性保留，不再使用

    selectorobject

    A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.

    .spec.caConfig

    Type
    object
    PropertyTypeDescription
    certmanagerobject

    Certmanager is generated CA for Istio

    insecureobject

    Deprecated: Insecure, use Certmanager instead For compatibility reasons, insecure CA is used by default

    .spec.caConfig.certmanager

    Description
    Certmanager is generated CA for Istio
    Type
    object

    .spec.caConfig.insecure

    Description
    Deprecated: Insecure, use Certmanager instead For compatibility reasons, insecure CA is used by default
    Type
    object

    .spec.clusters

    Type
    array

    .spec.clusters[]

    Type
    string

    .spec.istioConfig

    Type
    object
    PropertyTypeDescription
    localityLbSettingobject

    Locality-weighted load balancing allows administrators to control the distribution of traffic to endpoints based on the localities of where the traffic originates and where it will terminate. These localities are specified using arbitrary labels that designate a hierarchy of localities in {region}/{zone}/{sub-zone} form. For additional detail refer to Locality Weight The following example shows how to setup locality weights mesh-wide. Given a mesh with workloads and their service deployed to "us-west/zone1/" and "us-west/zone2/". This example specifies that when traffic accessing a service originates from workloads in "us-west/zone1/", 80% of the traffic will be sent to endpoints in "us-west/zone1/", i.e the same zone, and the remaining 20% will go to endpoints in "us-west/zone2/". This setup is intended to favor routing traffic to endpoints in the same locality. A similar setting is specified for traffic originating in "us-west/zone2/".

    distribute: - from: us-west/zone1/* to: "us-west/zone1/*": 80 "us-west/zone2/*": 20 - from: us-west/zone2/* to: "us-west/zone1/*": 20 "us-west/zone2/*": 80

    If the goal of the operator is not to distribute load across zones and regions but rather to restrict the regionality of failover to meet other operational requirements an operator can set a 'failover' policy instead of a 'distribute' policy. The following example sets up a locality failover policy for regions. Assume a service resides in zones within us-east, us-west & eu-west this example specifies that when endpoints within us-east become unhealthy traffic should failover to endpoints in any zone or sub-zone within eu-west and similarly us-west should failover to us-east.

    failover: - from: us-east to: eu-west - from: us-west to: us-east

    .spec.istioConfig.localityLbSetting

    Description
    Locality-weighted load balancing allows administrators to control the distribution of traffic to endpoints based on the localities of where the traffic originates and where it will terminate. These localities are specified using arbitrary labels that designate a hierarchy of localities in {region}/{zone}/{sub-zone} form. For additional detail refer to [Locality Weight](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/locality_weight) The following example shows how to setup locality weights mesh-wide. Given a mesh with workloads and their service deployed to "us-west/zone1/*" and "us-west/zone2/*". This example specifies that when traffic accessing a service originates from workloads in "us-west/zone1/*", 80% of the traffic will be sent to endpoints in "us-west/zone1/*", i.e the same zone, and the remaining 20% will go to endpoints in "us-west/zone2/*". This setup is intended to favor routing traffic to endpoints in the same locality. A similar setting is specified for traffic originating in "us-west/zone2/*". ```yaml distribute: - from: us-west/zone1/* to: "us-west/zone1/*": 80 "us-west/zone2/*": 20 - from: us-west/zone2/* to: "us-west/zone1/*": 20 "us-west/zone2/*": 80 ``` If the goal of the operator is not to distribute load across zones and regions but rather to restrict the regionality of failover to meet other operational requirements an operator can set a 'failover' policy instead of a 'distribute' policy. The following example sets up a locality failover policy for regions. Assume a service resides in zones within us-east, us-west & eu-west this example specifies that when endpoints within us-east become unhealthy traffic should failover to endpoints in any zone or sub-zone within eu-west and similarly us-west should failover to us-east. ```yaml failover: - from: us-east to: eu-west - from: us-west to: us-east ```
    Type
    object
    PropertyTypeDescription
    distributearray

    Explicitly specify loadbalancing weight across different zones and geographical locations. Refer to Locality weighted load balancing If empty, the locality weight is set according to the endpoints number within it.

    enabledboolean

    e.g. true means that turn on locality load balancing for this DestinationRule no matter what mesh wide settings is.

    failoverarray

    Optional: only one of distribute, failover or failoverPriority can be set. Explicitly specify the region traffic will land on when endpoints in local region becomes unhealthy. Should be used together with OutlierDetection to detect unhealthy endpoints. Note: if no OutlierDetection specified, this will not take effect.

    failoverPriorityarray

    failoverPriority is an ordered list of labels used to sort endpoints to do priority based load balancing. This is to support traffic failover across different groups of endpoints. Suppose there are total N labels specified:

    1. Endpoints matching all N labels with the client proxy have priority P(0) i.e. the highest priority. 2. Endpoints matching the first N-1 labels with the client proxy have priority P(1) i.e. second highest priority. 3. By extension of this logic, endpoints matching only the first label with the client proxy has priority P(N-1) i.e. second lowest priority. 4. All the other endpoints have priority P(N) i.e. lowest priority. Note: For a label to be considered for match, the previous labels must match, i.e. nth label would be considered matched only if first n-1 labels match. It can be any label specified on both client and server workloads. The following labels which have special semantic meaning are also supported:
    • topology.istio.io/network is used to match the network metadata of an endpoint, which can be specified by pod/namespace label topology.istio.io/network, sidecar env ISTIO_META_NETWORK or MeshNetworks. - topology.istio.io/cluster is used to match the clusterID of an endpoint, which can be specified by pod label topology.istio.io/cluster or pod env ISTIO_META_CLUSTER_ID. - topology.kubernetes.io/region is used to match the region metadata of an endpoint, which maps to Kubernetes node label topology.kubernetes.io/region or the deprecated label failure-domain.beta.kubernetes.io/region. - topology.kubernetes.io/zone is used to match the zone metadata of an endpoint, which maps to Kubernetes node label topology.kubernetes.io/zone or the deprecated label failure-domain.beta.kubernetes.io/zone. - topology.istio.io/subzone is used to match the subzone metadata of an endpoint, which maps to Istio node label topology.istio.io/subzone. The below topology config indicates the following priority levels: yaml failoverPriority: - "topology.istio.io/network" - "topology.kubernetes.io/region" - "topology.kubernetes.io/zone" - "topology.istio.io/subzone"
    1. endpoints match same [network, region, zone, subzone] label with the client proxy have the highest priority. 2. endpoints have same [network, region, zone] label but different [subzone] label with the client proxy have the second highest priority. 3. endpoints have same [network, region] label but different [zone] label with the client proxy have the third highest priority. 4. endpoints have same [network] but different [region] labels with the client proxy have the fourth highest priority. 5. all the other endpoints have the same lowest priority. Optional: only one of distribute, failover or failoverPriority can be set. And it should be used together with OutlierDetection to detect unhealthy endpoints, otherwise has no effect.

    .spec.istioConfig.localityLbSetting.distribute

    Description
    Explicitly specify loadbalancing weight across different zones and geographical locations. Refer to [Locality weighted load balancing](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/locality_weight) If empty, the locality weight is set according to the endpoints number within it.
    Type
    array

    .spec.istioConfig.localityLbSetting.distribute[]

    Description
    Describes how traffic originating in the 'from' zone or sub-zone is distributed over a set of 'to' zones. Syntax for specifying a zone is {region}/{zone}/{sub-zone} and terminal wildcards are allowed on any segment of the specification. Examples: `*` - matches all localities `us-west/*` - all zones and sub-zones within the us-west region `us-west/zone-1/*` - all sub-zones within us-west/zone-1
    Type
    object
    PropertyTypeDescription
    fromstring

    Originating locality, '/' separated, e.g. 'region/zone/sub_zone'.

    toobject

    Map of upstream localities to traffic distribution weights. The sum of all weights should be 100. Any locality not present will receive no traffic.

    .spec.istioConfig.localityLbSetting.distribute[].to

    Description
    Map of upstream localities to traffic distribution weights. The sum of all weights should be 100. Any locality not present will receive no traffic.
    Type
    object

    .spec.istioConfig.localityLbSetting.failover

    Description
    Optional: only one of distribute, failover or failoverPriority can be set. Explicitly specify the region traffic will land on when endpoints in local region becomes unhealthy. Should be used together with OutlierDetection to detect unhealthy endpoints. Note: if no OutlierDetection specified, this will not take effect.
    Type
    array

    .spec.istioConfig.localityLbSetting.failover[]

    Description
    Specify the traffic failover policy across regions. Since zone and sub-zone failover is supported by default this only needs to be specified for regions when the operator needs to constrain traffic failover so that the default behavior of failing over to any endpoint globally does not apply. This is useful when failing over traffic across regions would not improve service health or may need to be restricted for other reasons like regulatory controls.
    Type
    object
    PropertyTypeDescription
    fromstring

    Originating region.

    tostring

    Destination region the traffic will fail over to when endpoints in the 'from' region becomes unhealthy.

    .spec.istioConfig.localityLbSetting.failoverPriority

    Description
    failoverPriority is an ordered list of labels used to sort endpoints to do priority based load balancing. This is to support traffic failover across different groups of endpoints. Suppose there are total N labels specified: 1. Endpoints matching all N labels with the client proxy have priority P(0) i.e. the highest priority. 2. Endpoints matching the first N-1 labels with the client proxy have priority P(1) i.e. second highest priority. 3. By extension of this logic, endpoints matching only the first label with the client proxy has priority P(N-1) i.e. second lowest priority. 4. All the other endpoints have priority P(N) i.e. lowest priority. Note: For a label to be considered for match, the previous labels must match, i.e. nth label would be considered matched only if first n-1 labels match. It can be any label specified on both client and server workloads. The following labels which have special semantic meaning are also supported: - `topology.istio.io/network` is used to match the network metadata of an endpoint, which can be specified by pod/namespace label `topology.istio.io/network`, sidecar env `ISTIO_META_NETWORK` or MeshNetworks. - `topology.istio.io/cluster` is used to match the clusterID of an endpoint, which can be specified by pod label `topology.istio.io/cluster` or pod env `ISTIO_META_CLUSTER_ID`. - `topology.kubernetes.io/region` is used to match the region metadata of an endpoint, which maps to Kubernetes node label `topology.kubernetes.io/region` or the deprecated label `failure-domain.beta.kubernetes.io/region`. - `topology.kubernetes.io/zone` is used to match the zone metadata of an endpoint, which maps to Kubernetes node label `topology.kubernetes.io/zone` or the deprecated label `failure-domain.beta.kubernetes.io/zone`. - `topology.istio.io/subzone` is used to match the subzone metadata of an endpoint, which maps to Istio node label `topology.istio.io/subzone`. The below topology config indicates the following priority levels: ```yaml failoverPriority: - "topology.istio.io/network" - "topology.kubernetes.io/region" - "topology.kubernetes.io/zone" - "topology.istio.io/subzone" ``` 1. endpoints match same [network, region, zone, subzone] label with the client proxy have the highest priority. 2. endpoints have same [network, region, zone] label but different [subzone] label with the client proxy have the second highest priority. 3. endpoints have same [network, region] label but different [zone] label with the client proxy have the third highest priority. 4. endpoints have same [network] but different [region] labels with the client proxy have the fourth highest priority. 5. all the other endpoints have the same lowest priority. Optional: only one of distribute, failover or failoverPriority can be set. And it should be used together with `OutlierDetection` to detect unhealthy endpoints, otherwise has no effect.
    Type
    array

    .spec.istioConfig.localityLbSetting.failoverPriority[]

    Type
    string

    .spec.meshCommonConfig

    Type
    object
    PropertyTypeDescription
    elasticsearchobject
    isDefaultMonitorboolean
    istioSidecarobject

    Deprecated: IstioSidecar

    jaegerobject
    kafkaobject
    monitorTypestring
    prometheusBasicAuthobject
    prometheusURLstring
    traceSamplingnumber

    Deprecated: TraceSampling

    .spec.meshCommonConfig.elasticsearch

    Type
    object
    PropertyTypeDescription
    enabledboolean
    isDefaultboolean
    passwordstring
    secretNamestring
    secretNamespacestring
    urlstring
    usernamestring

    .spec.meshCommonConfig.istioSidecar

    Description
    Deprecated: IstioSidecar
    Type
    object
    PropertyTypeDescription
    cpuValuestring
    memoryValuestring

    .spec.meshCommonConfig.jaeger

    Type
    object
    PropertyTypeDescription
    indexPrefixstring
    strategystring

    .spec.meshCommonConfig.kafka

    Type
    object
    PropertyTypeDescription
    authenticationstring
    enabledboolean
    passwordstring
    secretNamestring
    secretNamespacestring
    tlsobject
    urlstring
    usernamestring

    .spec.meshCommonConfig.kafka.tls

    Type
    object
    PropertyTypeDescription
    enabledboolean
    secretNamestring
    secretNamespacestring

    .spec.meshCommonConfig.prometheusBasicAuth

    Type
    object
    PropertyTypeDescription
    enabledboolean
    passwordstring
    secretNamestring
    secretNamespacestring
    usernamestring

    .spec.meshConfig

    Type
    object

    .spec.multiCluster

    Type
    object
    PropertyTypeDescription
    enabledboolean

    Indicates that whether the multi-cluster feature is enabled.

    isMultiNetworkboolean

    Indicates whether the servicemeshgroup is targeting a multi-network environment.

    .spec.selector

    Description
    A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
    Type
    object
    PropertyTypeDescription
    matchExpressionsarray

    matchExpressions is a list of label selector requirements. The requirements are ANDed.

    matchLabelsobject

    matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed.

    .spec.selector.matchExpressions

    Description
    matchExpressions is a list of label selector requirements. The requirements are ANDed.
    Type
    array

    .spec.selector.matchExpressions[]

    Description
    A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
    Type
    object
    Required
    keyoperator
    PropertyTypeDescription
    keystring

    key is the label key that the selector applies to.

    operatorstring

    operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.

    valuesarray

    values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.

    .spec.selector.matchExpressions[].values

    Description
    values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
    Type
    array

    .spec.selector.matchExpressions[].values[]

    Type
    string

    .spec.selector.matchLabels

    Description
    matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed.
    Type
    object

    .status

    Description
    ServiceMeshGroupStatus defines the observed state of ServiceMeshGroup
    Type
    object
    PropertyTypeDescription
    clusterCountinteger
    latestUpdateTimestring
    meshStatusobject

    Individual status of each component controlled by the operator. The map key is the name of the component.

    messagestring

    Optional message providing additional information about the existing overall status.

    nonReadyClusterCountinteger
    nonReadyClustersarray
    statusstring

    Overall status of all clusters controlled by the operator.

    • If all clusters have status NONE, overall status is NONE. * If all clusters are HEALTHY, overall status is HEALTHY. * If one or more clusters are RECONCILING and others are HEALTHY, overall status is RECONCILING. * If one or more clusters are UPDATING and others are HEALTHY, overall status is UPDATING. * If clusters are a mix of RECONCILING, UPDATING and HEALTHY, overall status is UPDATING. * If any component is in ERROR state, overall status is ERROR. * If further action is needed for reconciliation to proceed, overall status is ACTION_REQUIRED.

    .status.meshStatus

    Description
    Individual status of each component controlled by the operator. The map key is the name of the component.
    Type
    object

    .status.nonReadyClusters

    Type
    array

    .status.nonReadyClusters[]

    Type
    string

    API Endpoints

    The following API endpoints are available:

    • /apis/asm.alauda.io/v1alpha1/namespaces/{namespace}/servicemeshgroups
      • DELETE: delete collection of ServiceMeshGroup
      • GET: list objects of kind ServiceMeshGroup
      • POST: create a new ServiceMeshGroup
    • /apis/asm.alauda.io/v1alpha1/namespaces/{namespace}/servicemeshgroups/{name}
      • DELETE: delete the specified ServiceMeshGroup
      • GET: read the specified ServiceMeshGroup
      • PATCH: partially update the specified ServiceMeshGroup
      • PUT: replace the specified ServiceMeshGroup
    • /apis/asm.alauda.io/v1alpha1/namespaces/{namespace}/servicemeshgroups/{name}/status
      • GET: read status of the specified ServiceMeshGroup
      • PATCH: partially update status of the specified ServiceMeshGroup
      • PUT: replace status of the specified ServiceMeshGroup

    /apis/asm.alauda.io/v1alpha1/namespaces/{namespace}/servicemeshgroups

    HTTP method
    DELETE
    Description
    delete collection of ServiceMeshGroup
    HTTP responses
    HTTP codeResponse body
    200 - OKStatus schema
    401 - UnauthorizedEmpty
    HTTP method
    GET
    Description
    list objects of kind ServiceMeshGroup
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroupList schema
    401 - UnauthorizedEmpty
    HTTP method
    POST
    Description
    create a new ServiceMeshGroup
    Query parameters
    ParameterTypeDescription
    dryRunstringWhen present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
    fieldValidationstringfieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
    Body parameters
    ParameterTypeDescription
    bodyServiceMeshGroup schemaapplication/json formatted
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    201 - CreatedServiceMeshGroup schema
    202 - AcceptedServiceMeshGroup schema
    401 - UnauthorizedEmpty

    /apis/asm.alauda.io/v1alpha1/namespaces/{namespace}/servicemeshgroups/{name}

    HTTP method
    DELETE
    Description
    delete the specified ServiceMeshGroup
    Query parameters
    ParameterTypeDescription
    dryRunstringWhen present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
    HTTP responses
    HTTP codeResponse body
    200 - OKStatus schema
    202 - AcceptedStatus schema
    401 - UnauthorizedEmpty
    HTTP method
    GET
    Description
    read the specified ServiceMeshGroup
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    401 - UnauthorizedEmpty
    HTTP method
    PATCH
    Description
    partially update the specified ServiceMeshGroup
    Query parameters
    ParameterTypeDescription
    dryRunstringWhen present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
    fieldValidationstringfieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    401 - UnauthorizedEmpty
    HTTP method
    PUT
    Description
    replace the specified ServiceMeshGroup
    Query parameters
    ParameterTypeDescription
    dryRunstringWhen present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
    fieldValidationstringfieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
    Body parameters
    ParameterTypeDescription
    bodyServiceMeshGroup schemaapplication/json formatted
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    201 - CreatedServiceMeshGroup schema
    401 - UnauthorizedEmpty

    /apis/asm.alauda.io/v1alpha1/namespaces/{namespace}/servicemeshgroups/{name}/status

    HTTP method
    GET
    Description
    read status of the specified ServiceMeshGroup
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    401 - UnauthorizedEmpty
    HTTP method
    PATCH
    Description
    partially update status of the specified ServiceMeshGroup
    Query parameters
    ParameterTypeDescription
    dryRunstringWhen present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
    fieldValidationstringfieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    401 - UnauthorizedEmpty
    HTTP method
    PUT
    Description
    replace status of the specified ServiceMeshGroup
    Query parameters
    ParameterTypeDescription
    dryRunstringWhen present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
    fieldValidationstringfieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
    Body parameters
    ParameterTypeDescription
    bodyServiceMeshGroup schemaapplication/json formatted
    HTTP responses
    HTTP codeResponse body
    200 - OKServiceMeshGroup schema
    201 - CreatedServiceMeshGroup schema
    401 - UnauthorizedEmpty