New Application Connectivity tests - Test suite for Compass Runtime Agent

[akgalwas]

Description

We need an integration test of Compass Runtime Agent. The test should be implemented with a similar structure to the Application Gateway test. It should be fast, simple, and easy to maintain. If something breaks on some end-to-end pipeline or some environment, this test should clearly tell if there is a problem with the Compass Runtime Agent or not

Acceptance criteria

• A test checking Compass Runtime Agent functionality is implemented
• The test takes minimal possible execution time
• The test is considered as easy to maintain and has a similar structure to the Application Gateway tests
• The test runs on the Prow pipeline
• The test is runnable locally/ on a custom cluster

Attachments

epic issue - #13977

[akgalwas]

Work plan:

Phase 1

• Prepare and merge initial PR with project structure. It should contain: Dockerfile, Makefile and minimal code changes that could be run on a Prow pipeline. @mvshao @akgalwas
• Prepare a testcase structure and define interfaces for creating Applications and comparing applications PR @akgalwas
• Prepare changes in makefile and charts structure @koala7659 PR
• Prepare changes in pipelines to align to makefiles changes PR
• Implement code for comparing CRDs and secrets done PR @mvshao
• Modify test pipeline to pass environment variables with credentials (clientID, clientSecret, etc.) to review @franpog859 @koala7659 (Restore jobs for testing compass-runtime-agent test-infra#5977)
• Implement graphQL client to register applications in compass director done @koala7659 (Cra test gql to compass #15119)
• Implement code configuring Compass Runtime Agent @akgalwas @franpog859 Prepare code initializing Compass Runtime Agent before Compass Runtime Agent runs #15390
• Re-enable compass-runtime-agent pipeline on prow done @koala7659 Restore jobs for testing compass-runtime-agent test-infra#5977
• Add the README @mvshao @akgalwas @majakurcius Compass Runtime Agent tests - readme #15566

Phase 2

• Enhance code creating Application in Director to cover API Packages Cover case with API Bundles in the Compass Runtime Agent tests #16453
• Implement testcase for updating Applications Implement update test #16397
  • Prepare code for updating existing Applications in Director
  • Implement test verifying that Compass Runtime Agent updated applications as expected
• Implement testcase for deleting Applications CRI delete app test #16239
  • Implement test verifying that Compass Runtime Agent deleted applications as expected
• Update the README

[franpog859]

Please, remember to use the new Compass Director API in regard to the scenarios. It's described for example there and there

[Disper]

Should this pipeline be enabled before it's ready? It's failing in PRs such as this one and might be confusing for people.

[franpog859]

Please, create a ticket for the additional follow-up that covers all the possible Compass Runtime Agent cases, that covers ADDITIONAL cases in regards to the manual tests. These are the things that need to be done:

• Maintaining Compass connection:
  • Compass Runtime Agent fetches certificates from Compass Connector and stores them in Secrets
  • Compass Runtime Agent renews the certificate if it is about to expire
  • Compass Runtime Agent renews the certificate if the resyncNow flag is set to true
• Labeling a Runtime with the Eventing URL

[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

[kyma-bot]

This issue or PR has been automatically closed due to the lack of 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

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

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.