At this moment migration procedure from v1beta1 to v2alpha1 may cause fairly short downtime. Applying APIRule in v2alpha1 version would cause removal of ORY Oathkeeper related resources and creation of Istio related resources. From user point of view migration should introduce necessary changes and should not involve changes required in clients calling the workload.
There should be possibility to migrate from APIRule v1beta1 version to v2alpha1 version by applying updated specification. This operation should not cause any downtime. Migration logic should be implemented as described in https://github.com/kyma-project/api-gateway/issues/1128.
ACs:
[ ] migration logic implemented
[ ] migration is not causing any downtime
[ ] documentation updated
Reasons
Provide possibility to migrate to v2alpha1 version without downtime
DoD:
[ ] Provide unit and integration tests.
[ ] Provide documentation.
[ ] Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
[ ] If you changed the resource limits, explain why it was needed.
[ ] Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
Description
At this moment migration procedure from v1beta1 to v2alpha1 may cause fairly short downtime. Applying APIRule in v2alpha1 version would cause removal of ORY Oathkeeper related resources and creation of Istio related resources. From user point of view migration should introduce necessary changes and should not involve changes required in clients calling the workload.
There should be possibility to migrate from APIRule v1beta1 version to v2alpha1 version by applying updated specification. This operation should not cause any downtime. Migration logic should be implemented as described in https://github.com/kyma-project/api-gateway/issues/1128.
ACs:
Reasons
Provide possibility to migrate to v2alpha1 version without downtime
DoD:
Attachments part of: https://github.com/kyma-project/api-gateway/issues/939