Help Center/ Application Service Mesh/ User Guide/ Mesh Configuration/ Istio Resource Management/ Handling Policy of Resource Configuration Using YAML
Updated on 2023-06-13 GMT+08:00

Handling Policy of Resource Configuration Using YAML

You can create Istio resources on the console or using YAML on the Istio Resource Management page. To avoid configuration conflicts, you are advised to:

  • Use console to maintain resources created on the console.
  • Use YAML to maintain resources created by YAML.

If resources created on the console are modified using YAML, the corresponding functions on the console will be unavailable. For example, after VirtualService resources are configured using YAML, the corresponding services on the console cannot perform traffic management and grayscale release.

Handling Policy

When you edit or create Istio resources for a service on the Mesh Configuration > Istio Resource Management page, Apply YAML only at the bottom of the page is selected by default. Retain the selection and click OK, the configuration takes effect, however, some functions on the console are no longer available for the service and the resources can be maintained only in YAML mode.

If Apply YAML only is not selected, the modified configuration using YAML may conflict with some console functions.

Table 1 Impacts on console functions when Apply YAML only is selected

Symptom

Possible Cause

On the Service Management page, the Security button of the target service is unavailable.

The AuthorizationPolicy resource is modified using YAML.

On the Service Management page, the Manage Traffic button of the target service is unavailable.

The DestinationRule or VirtualService resource is modified using YAML.

On the Service Management page, the Release button of the target service is unavailable.

The DestinationRule or VirtualService resource is modified using YAML.

When a release task is created on the Grayscale Release page, the target service cannot be selected.

The DestinationRule or VirtualService resource is modified using YAML.

On the Gateway Management page, the Add Route button of the target gateway is unavailable.

Gateway resources are modified using YAML.

When a route is added on the Gateway Management page, the target service cannot be selected.

The DestinationRule or VirtualService resource is modified using YAML.