You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 18, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+7-24Lines changed: 7 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Create a Kubernetes cluster with either [Minikube](https://kubernetes.io/docs/ge
52
52
If you want to use the Bluemix Container Registry start by [Uploading the images](docs/use-bluemix-container-registry.md) to the Bluemix Container Registry.
53
53
54
54
### Deploy using DevOps Toolchain to Kubernetes Cluster from Bluemix Container Service
55
-
If you want to deploy the Gitlab directly to Bluemix, click on 'Deploy to Bluemix' button below to create a [Bluemix DevOps service toolchain and pipeline](https://console.ng.bluemix.net/docs/services/ContinuousDelivery/toolchains_about.html#toolchains_about) for deploying the Gitlab sample, else jump to [Steps](#steps)
55
+
If you want to deploy the Gitlab directly to Bluemix, click on `Deploy to Bluemix` button below to create a [Bluemix DevOps service toolchain and pipeline](https://console.ng.bluemix.net/docs/services/ContinuousDelivery/toolchains_about.html#toolchains_about) for deploying the Gitlab sample, else jump to [Steps](#steps)
After you have created all the services and deployments, wait for 3 to 5 minutes. You can check the status of your deployment on Kubernetes UI. Run 'kubectl proxy' and go to URL 'http://127.0.0.1:8001/ui' to check when the GitLab container becomes ready.
92
+
After you have created all the services and deployments, wait for 3 to 5 minutes. You can check the status of your deployment on Kubernetes UI. Run `kubectl proxy` and go to URL 'http://127.0.0.1:8001/ui' to check when the GitLab container becomes ready.
93
93
94
94

95
95
96
96
Next [retrieve your external ip and port for GitLab](#2-retrieve-external-ip-and-port-for-GitLab)
97
97
98
98
##### 1.2 Use PostgreSQL from Bluemix
99
99
100
-
Use the Bluemix catalog or the bx command to create a service instance of Compose for PostgreSQL and add a set of credentials.
100
+
Use the Bluemix catalog or the `bx` command to create a service instance of Compose for PostgreSQL and add a set of credentials.
101
101
102
102
```bash
103
103
$ bx service create compose-for-postgresql Standard "Compose for PostgreSQL-GL"
@@ -112,7 +112,7 @@ $ bx service key-show "Compose for PostgreSQL-GL" "Credentials-1" | grep "postgr
Modify your ```kubernetes/gitlab-postgres-svc.yaml``` file and replace COMPOSE_PG_PASSWORD with the password, COMPOSE_PG_HOST with the hostname, and COMPOSE_PG_PORT with the port.
115
+
Modify your ```kubernetes/gitlab-postgres-svc.yaml``` file and replace `COMPOSE_PG_PASSWORD` with the password, `COMPOSE_PG_HOST` with the hostname, and `COMPOSE_PG_PORT` with the port.
116
116
117
117
Using the above example, the ```env:``` section will look like this.
After you have created all the services and deployments, wait for 3 to 5 minutes. You can check the status of your deployment on Kubernetes UI. Run 'kubectl proxy' and go to URL 'http://127.0.0.1:8001/ui' to check when the GitLab container becomes ready.
148
+
After you have created all the services and deployments, wait for 3 to 5 minutes. You can check the status of your deployment on Kubernetes UI. Run `kubectl proxy` and go to URL 'http://127.0.0.1:8001/ui' to check when the GitLab container becomes ready.
149
149
150
150

151
151
@@ -163,9 +163,9 @@ NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
> Note: The 30080 port is for gitlab UI and the 30022 port is for ssh.
166
+
> Note: The `30080` port is for gitlab UI and the `30022` port is for ssh.
167
167
168
-
> Note: The gitlab external url is set to `gitlab.example.com` add this to your hosts file pointing to your IP address from above in order to use the url that gitlab expects. If you can't do this, then using the IP (in this example 169.47.241.22) should work.
168
+
> Note: The gitlab external url is set to `gitlab.example.com` add this to your hosts file pointing to your IP address from above in order to use the url that gitlab expects. If you can't do this, then using the IP (in this example `169.47.241.22`) should work.
169
169
170
170
> Note: If you using Minikube for local kubernetes deployment, you can access the list of service IPs using the `minikube service list` command.
171
171
@@ -204,23 +204,6 @@ bx service key-delete "Compose for PostgreSQL-GL" Credentials-1
204
204
bx service delete "Compose for PostgreSQL-GL"
205
205
```
206
206
207
-
# Privacy Notice
208
-
209
-
Sample Kubernetes Yaml file that includes this package may be configured to track deployments to [IBM Cloud](https://www.bluemix.net/) and other Kubernetes platforms. The following information is sent to a [Deployment Tracker](https://github.com/IBM/metrics-collector-service) service on each deployment:
* Kubernetes Cluster ID (Only from IBM Cloud's cluster)
214
-
* Kubernetes Customer ID (Only from IBM Cloud's cluster)
215
-
* Environment variables in this Kubernetes Job.
216
-
217
-
This data is collected from the Kubernetes Job in the sample application's yaml file. This data is used by IBM to track metrics around deployments of sample applications to IBM Cloud to measure the usefulness of our examples so that we can continuously improve the content we offer to you. Only deployments of sample applications that include code to ping the Deployment Tracker service will be tracked.
218
-
219
-
## Disabling Deployment Tracking
220
-
221
-
Please comment out/remove the Metric Kubernetes Job portion in the 'kubernetes/github.yaml' file.
Copy file name to clipboardExpand all lines: docs/bluemix-postgres.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ bx cr images
40
40
41
41
# 2. Create Compose for PostgreSQL on Bluemix
42
42
43
-
Use the Bluemix catalog or the bx command to create a service instance of Compose for PostgreSQL and add a set of credentials.
43
+
Use the Bluemix catalog or the `bx` command to create a service instance of Compose for PostgreSQL and add a set of credentials.
44
44
45
45
```bash
46
46
bx service create compose-for-postgresql Standard "Compose for PostgreSQL-GL"
@@ -87,9 +87,9 @@ kubectl create -f redis.yaml
87
87
kubectl create -f gitlab-postgres-svc.yaml
88
88
```
89
89
90
-
After you have created all the services and deployments, wait for 3 to 5 minutes. You can check the status of your deployment on Kubernetes UI. Run 'kubectl proxy' and go to URL 'http://127.0.0.1:8001/ui' to check when the GitLab container becomes ready.
90
+
After you have created all the services and deployments, wait for 3 to 5 minutes. You can check the status of your deployment on Kubernetes UI. Run `kubectl proxy` and go to URL 'http://127.0.0.1:8001/ui' to check when the GitLab container becomes ready.
91
91
92
-

92
+

93
93
94
94
After few minutes run the following commands to get your public IP and NodePort number.
95
95
@@ -102,22 +102,22 @@ NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
0 commit comments