at this moment we have two different cluster spec files for testing
cluster-test.yaml and cluster-on-pvc-minikube.yaml. With the new
option user can choose which one to use to bootstrap the cluster
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
current code gets the ip:port for the dashboard by using
the ip of the mgr pods. This works great when there's only
one mgr but it fails in case of a multi-node cluster
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
adding support to specify operator and cluster namespaces through new
command-line arguments: -c for cluster and -o for operator. The script
will automatically update the namespace in the corresponding YAML files
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
This change to the create-dev-cluster script is intended to make the
handling of invalid invocations more uniform
examples are unknown options and options requiring an argument specified
without one.
The unification is achieved by encapsulating the corresponding code in a
function.
Signed-off-by: Michael Adam <obnox@samba.org>
This change introduce a new argument -p to specify the minikube
profile for the new cluster. This way we can have multiple rook
clusters running on the same machine.
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
Let's use the minikube profiles feature to set up a unique profile
exclusively for the Rook cluster. By doing this, we make sure that we
don't run into any issues with other minikube profiles that users
might already have in their local setup.
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
The new create-dev-cluster script errored out for me, not finding the
deploy/examples directory.
This change fixes that problem by making the path relative to the
script's directory, so that it works in a rook code tree from where it
is expected to be run.
Signed-off-by: Michael Adam <obnox@samba.org>
Adding a new '-m' option for activating monitoring during
cluster setup. With this option turned on, the script will handle the
installation of the monitoring stack and configure the dashboard to
connect to the newly installed Prometheus server automatically.
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
Redouane Kachach
Michael Adam