mirror of
https://github.com/submariner-io/submariner-charts.git
synced 2026-09-21 03:20:35 +00:00
Daniel FarrellandThomas Pantelis
eea398da4e
Per GitHub's security guidelines, GHAs should be pinned using full length commit SHAs instead of tags. The SHAs are of the commits currently resolved by the versions. Even "trusted" GHAs from GitHub developers are pinned because it's possible their repo rights could be compromised and a malicious GHA published. These core repos are not frequently substantially updated. Submariner-internal GHAs are left pinned at devel because we want automatic updates from Shipyard's shared tooling. Signed-off-by: Daniel Farrell <dfarrell@redhat.com>
submariner-charts
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.