-
Notifications
You must be signed in to change notification settings - Fork 21
Conversation
|
||
1. Run the Minikube: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we can just have a short script under the hack
folder so user/developer will need to just execute
./hack/run-dev-kind.sh
this script can even automate that kind and helm will be downloaded for you if you will specify additional flag, we already have some helpers for that in /hack/ci dir.
so sth like:
./hack/run-dev-kind.sh --skip-deps-installation # such thing will resuse your own kind and helm
# or
./hack/run-dev-kind.sh --install-deps # such thing will install own kind and helm instead of reusing your own
I do not have strong preferences if skip or install is a better approach
WDYT?
because copying that each time is boring :(
README.md
Outdated
* [Helm CLI](https://github.com/kubernetes/helm#install) | ||
* [Minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/) for local installation | ||
* [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) 1.16 | ||
* [Helm CLI](https://github.com/kubernetes/helm#install) 2.10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why we cannot use helm 2.14 or 2.15?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested. can be :)
README.md
Outdated
helm init --wait | ||
``` | ||
|
||
3. Create ServiceAccount for Tiller with admin privileges |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imo it should be in different order:
shout '- Installing Tiller...'
kubectl --namespace kube-system create sa tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
helm init --service-account tiller --upgrade --wait
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Order is the same: create serviceaccount
, create clusterrolebinding
,
the difference is the last command: helm init
instead patch deploy
. Do you mean change command? Is there something wrong with patch
?
├── docs # Documentation files | ||
├── hack # Various scripts that are used by Helm Broker developers | ||
├── internal # Private application and library code | ||
├── pkg # Library code to use by external applications |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you add also short readme to pkg, similar to this one: https://github.com/kyma-project/helm-broker/tree/master/hack
this folder is quite important and IMO is good to have a clear statement about its purpose
same thing for test
folder, so it's dedicated for integrations/e2e etc. do not store there e.g. verify-gofmt.sh script, or sth similar because such thing should be placed under /hack dir.
README.md
Outdated
* [Minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/) for local installation | ||
* [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) 1.16 | ||
* [Helm CLI](https://github.com/kubernetes/helm#install) 2.10 | ||
* [docker](https://docs.docker.com/install/) 19.03 (for local installation) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* [docker](https://docs.docker.com/install/) 19.03 (for local installation) | |
* [Docker](https://docs.docker.com/install/) 19.03 (for local installation) |
README.md
Outdated
* [docker](https://docs.docker.com/install/) 19.03 (for local installation) | ||
* [Kind](https://github.com/kubernetes-sigs/kind#installation-and-usage) 0.5 (for local installation) | ||
|
||
for non-local installation (without kind) use Kubernetes in version 1.15 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for non-local installation (without kind) use Kubernetes in version 1.15 | |
>**NOTE:** For non-local installation, use Kubernetes v1.15. |
README.md
Outdated
|
||
1. Run the Minikube: | ||
1. Create local cluster with Kind (making sure the docker is turned on): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Create local cluster with Kind (making sure the docker is turned on): | |
1. Create a local cluster on Kind: |
README.md
Outdated
helm init --wait | ||
``` | ||
|
||
3. Create ServiceAccount for Tiller with admin privileges |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3. Create ServiceAccount for Tiller with admin privileges | |
3. Create a ServiceAccount for Tiller with admin privileges: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
outdated
README.md
Outdated
``` | ||
|
||
3. Install the Service Catalog as a Helm chart: | ||
4. Install the Service Catalog as a Helm chart: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4. Install the Service Catalog as a Helm chart: | |
4. Install Service Catalog as a Helm chart: |
README.md
Outdated
```bash | ||
helm repo add svc-cat https://svc-catalog-charts.storage.googleapis.com | ||
helm install svc-cat/catalog --name catalog --namespace catalog | ||
``` | ||
|
||
4. Install the Helm Broker chart: | ||
5. Clone Helm Broker repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5. Clone Helm Broker repository | |
5. Clone the Helm Broker repository: |
README.md
Outdated
├── config # Configuration file templates or default configs | ||
├── deploy # Dockerfiles to build images | ||
├── docs # Documentation files | ||
├── hack # Various scripts that are used by Helm Broker developers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
├── hack # Various scripts that are used by Helm Broker developers | |
├── hack # Scripts used by the Helm Broker developers |
README.md
Outdated
├── hack # Various scripts that are used by Helm Broker developers | ||
├── internal # Private application and library code | ||
├── pkg # Library code to use by external applications | ||
└── test # Additional external test apps and test data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
└── test # Additional external test apps and test data | |
└── test # Additional external test applications and test data |
README.md
Outdated
├── .github # Pull request and issue templates | ||
├── charts # Charts to install by Helm | ||
├── cmd # Main applications for project | ||
├── config # Configuration file templates or default configs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
├── config # Configuration file templates or default configs | |
├── config # Configuration file templates or default configurations |
helm init --service-account tiller --upgrade --wait | ||
} | ||
|
||
tiller::assert_tiller_is_up() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: this can be dropped because we already using the --wait
flag during the init action
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer to leave it, if everything will be ok then it is only one iteration and we will be sure tiller is up.
* [Docker](https://docs.docker.com/install/) 19.03 (for local installation) | ||
* [Kind](https://github.com/kubernetes-sigs/kind#installation-and-usage) 0.5 (for local installation) | ||
|
||
>**NOTE:** For non-local installation, use Kubernetes v1.15. | ||
|
||
## Installation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should somewhere describe that you can just execute the
./hack/run-dev-kind.sh
which will execute all those steps for you. Now it is a piece of secret knowledge.
IMO here we can have just info about this script with prerequisite and in the directory where this ./hack/run-dev-kind.sh
have details what is done under the hood and if someone wants to do it manually then can do it.
hack/run-dev-kind.sh
Outdated
|
||
set -o errexit | ||
|
||
readonly SUPPORTED_KIND_VERSION="v0.5.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just require this specified in deps_ver.sh
Related to #35