APIRule v2alpha1

[strekm]

Description

Introduce APIRule 1beta2 to showcase coming changes: dropping ORY Oathkeeper and closer integration with Istio (JWT and external authorizer). Users will have a chance to get familiar with API and breaking changes. This will also give opportunity to design migration path. Finally it is a way to collect feedback and harden implementation.

Assumption is that this version will be promoted to v1 without significant changes of API and functionality if it's possible.

Tasks:

• v1beta2 API proposal
• introducing version with breaking changes POC
• v2alpha1 renaming
• [POC] v1beta1 -> v2alpha1 migration
• migration mode
• refactoring
• implementation of no_auth and jwt
• adjust CORS default settings
• implementation of ext_auth
• mutators support
• short host support
• include v1beta2 in documentation
• blogpost
• UI

Reasons

Introduce changes to APIRule API

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.
• Add release notes.

Attachments
part of #322

[strekm]

Migration blog posts published:

• https://community.sap.com/t5/technology-blogs-by-sap/sap-btp-kyma-runtime-apirule-migration-noauth-and-jwt-handlers/ba-p/13882833
• https://community.sap.com/t5/technology-blogs-by-sap/sap-btp-kyma-runtime-apirule-migration-ory-oathkeeper-based-oauth2-handlers/ba-p/13896184

[strekm]

API Gateway 2.8.0 introducing UI supporting APIRule v2alpha1 in Kyma dashboard was rolled out to fast channel on 29.10 and it is scheduled to be promoted to regular channel on 12.11 for managed Kyma offering