Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Upgrade readme file #43

Merged
merged 3 commits into from
Oct 18, 2019
Merged

Upgrade readme file #43

merged 3 commits into from
Oct 18, 2019

Conversation

jasiu001
Copy link

Related to #35

@jasiu001 jasiu001 added area/documentation Issues or PRs related to documentation area/service-management Issues or PRs related to service management labels Oct 16, 2019
@jasiu001 jasiu001 added this to the Sprint_Gopher_28 milestone Oct 16, 2019

1. Run the Minikube:
Copy link
Contributor

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
Copy link
Contributor

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?

Copy link
Author

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
Copy link
Contributor

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

Copy link
Author

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
Copy link
Contributor

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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
3. Create ServiceAccount for Tiller with admin privileges
3. Create a ServiceAccount for Tiller with admin privileges:

Copy link
Author

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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
├── 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
└── 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
├── 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() {
Copy link
Contributor

@mszostok mszostok Oct 17, 2019

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

Copy link
Author

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
Copy link
Contributor

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.


set -o errexit

readonly SUPPORTED_KIND_VERSION="v0.5.1"
Copy link
Contributor

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

@jasiu001 jasiu001 merged commit 5886410 into SAP-archive:master Oct 18, 2019
@mszostok mszostok added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 23, 2019
@jasiu001 jasiu001 deleted the readme branch June 25, 2021 08:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/documentation Issues or PRs related to documentation area/service-management Issues or PRs related to service management kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants