Mike KolesnikandThomas Pantelis 7f4648985e Use minimal clusters for E2E
We don't really need to run the entire E2E suite anymore since we're
deploying the operator and it takes care of the entire deployment cycle.
Hence, the testing on operator should suffice and the helm testing can
be much slimmer and only use 2 single-node clusters.

This won't run the non-gw node tests, but as it's all tested on the
operator anyhow, there's no need to re-test it here.

Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>
2022-07-07 12:07:07 -04:00
2022-07-07 11:54:23 -04:00
2022-07-07 12:07:07 -04:00
2020-12-17 15:44:34 +01:00
2021-12-13 07:44:09 -05:00
2020-12-17 15:44:34 +01:00
2022-07-07 11:54:23 -04:00
2019-03-11 22:06:52 -07:00
2021-11-09 10:49:38 +01:00
2022-05-16 08:42:14 -04:00

submariner-charts

CII Best Practices Release Charts Periodic Flake Finder

Please see the Helm docs on Submariner's website.

Development workflow

Prerequisites

Create a fork and checkout

Create a fork of the original repository, clone it locally and checkout a new branch from master.

Example:

git clone https://github.com/myuser/submariner-charts.git
cd submariner-charts
git checkout -b new-feature

Now you can modify the Helm charts according to your needs.

Use the modified charts

Locally-modified charts can be installed using helm install, referring to the local path; for example:

helm install submariner-k8s-broker ./submariner-k8s-broker ...

In the base directory of this repository, a local deployment using the local charts can be obtained by running the following command:

make deploy

This will start two kind clusters and deploy Submariner using the Broker and Operator charts.

make e2e

will run the end-to-end test suite used to validate that Submariner is working correctly.

S
Description
No description provided
Readme
10 MiB
Languages
Shell 47.9%
Go Template 19.2%
Makefile 19%
Go 13.9%