component test for istio based jwt apirule creation

[strekm]

Description

Implement component test exposing httpbin with istio jwt apirule. Assuming cluster is created, kyma installed (only Istio is required) api-gateway controller is installed with FT on test should deploy httpbin workload and add it to service mesh. APIRule should be created with all possible fields (consider required scopes) and then httpbin endpoint called.

ACs:

• test deploys httpbin workload as a part of service mesh
• test creates apirule of type istio jwt with all possible fields
• test calles exposed endpoint
• test should be gherkinized

Reasons

automatisation of testing effort

DoD:
- [ ] provide documentation
- [ ] publish release notes and What's New updates for Kyma customers
- [ ] provide unit tests

• test on SKR
  - [ ] verify Get started guides
  - [ ] verify resource limits
• followup issue
  - [ ] create release and bump in kyma

PR

• API Gateway integration Istio jwt test #164

Attachments

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale