Kyma

Appearance

APIRule v2 Contains a Changed Status Schema ​

Symptom ​

There is a changed schema of status in an APIRule custom resource (CR), for example:

bash
kubectl get apirules.gateway.kyma-project.io -n $NAMESPACE $APIRULE_NAME -oyaml
yaml
  ...
  status:
    lastProcessedTime: "2025-04-25T11:16:11Z"
    state: Ready

Cause ​

The schema of the status.state field in the v2 APIRule CR introduces a unified approach, similar to the one used in the API Gateway CR. The possible states of the status.state field are Ready, Warning, Error, Processing, or Deleting.

Solution ​

To make sure that support for your APIRules is maintained, you must migrate them to version v2. To learn how to do this, follow the APIRule migration guide.

Specify explicitly v1beta1 version when requesting the APIRule resource to obtain the complete status:

bash
kubectl get apirules.v1beta1.gateway.kyma-project.io -n $NAMESPACE $APIRULE_NAME -oyaml
yaml
  ...
  status:
  APIRuleStatus:
    code: OK
  accessRuleStatus:
    code: OK
  lastProcessedTime: "2025-04-25T11:16:11Z"
  observedGeneration: 1
  virtualServiceStatus:
    code: OK