Automatic testing

[the1bit]

Description

Changes proposed in this pull request:

This Workflow can test the backend code automatically. Additionally, it can run test scripts.

Files and folders

• GitHub Action Workflow: .github/workflows
• Backend code: assistant/backend
• Kubernetes related scripts and deployment files: .scripts/kubernetes
• Shell scripts (k3s installation, deployment verification, test scripts): .scripts/shell

Secrets

• Secret for Backend (K3S_SECRET)
• Configmap for Backend (K3S_CONFIGMAP)
• User for sap-llm-commons (JFROG_IDENTITY_USER)
• Token for sap-llm-commons (JFROG_IDENTITY_TOKEN)

Steps

in .github/workflows/backend-e2e-test.yaml:

1. Get the code
2. Create local Docker image registry
3. Build local Docker image
4. Push image to local registry
5. Configure K3s for local Docker image registry
6. Install and configure K3s cluster
7. Verify K3s cluster
8. Deploy - Create namespace
9. Deploy - Create Secret for backend
10. Deploy - Create ConfigMap for backend
11. Deploy - Create Backend and NodePort service
12. Deploy - Wait for deployment
13. Test - Health check
14. Test - Cluster resources

Related issue(s)

[CLAassistant]

All committers have signed the CLA.

[kyma-bot]

New changes are detected. LGTM label has been removed.

[kyma-bot]

New changes are detected. LGTM label has been removed.