Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support to provide e2e testing configuration #641

Open
eromanova opened this issue Nov 15, 2024 · 0 comments
Open

Support to provide e2e testing configuration #641

eromanova opened this issue Nov 15, 2024 · 0 comments
Assignees

Comments

@eromanova
Copy link
Member

eromanova commented Nov 15, 2024

Currently, there is no straightforward way to provide overrides for our testing configuration. The templates and other configurations are hardcoded. There is a need to test more complex configurations, such as deploying two clusters with different templates on a single management cluster, testing the deployment of the N-1 template, and upgrading to the N template, among others.

Here is an example of testing configuration (it’s a draft. It can be changed/extended):

/test-e2e
aws:
  enabled: true
  standalone:
    upgrade: true
    template: aws-standalone-cp-0-0-3
    upgradeTemplate: aws-standalone-cp-0-0-4
  hosted:
    template: aws-hosted-cp-0-0-3
azure:
  enabled: true
  standalone:
    upgrade: true
  hosted:
    upgrade: false

If some configuration wasn’t provided it’ll be filled with defaults. Additionally, if the templates for deployment and upgrade are not specified in the configuration, they will be automatically detected. By default, the latest available templates from all the supported in the cluster namespace will be selected and tested.
The configuration will be parsed, encoded in b64, and passed to our Makefile test-e2e target as an env variable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant