From e7af6f5fea0bda15352a3fc3f849befe7fc9d944 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wolfgang=20Hu=C3=9F?= Date: Tue, 28 Sep 2021 09:02:35 +0200 Subject: [PATCH 1/3] Fix dummy IP and last README.md link --- deployment/kubernetes/DigitalOcean.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deployment/kubernetes/DigitalOcean.md b/deployment/kubernetes/DigitalOcean.md index 61998d7..f9cc3ef 100644 --- a/deployment/kubernetes/DigitalOcean.md +++ b/deployment/kubernetes/DigitalOcean.md @@ -67,7 +67,7 @@ Take one of the IPs of perhaps two or more droplets in your cluster from the lis To understand what makes sense to do when managing your DNS with DigitalOcean, you need to know how DNS works: -DNS means `Domain Name System`. It resolves domains like `example.com` into an IP like `123.123.123`. +DNS means `Domain Name System`. It resolves domains like `example.com` into an IP like `123.123.123.123`. DigitalOcean is not a domain registrar, but provides a DNS management service. If you use DigitalOcean's DNS management service, you can configure [your cluster](/deployment/kubernetes/README.md#dns) to always resolve the domain to the correct IP and automatically update it for that. The IPs of the DigitalOcean machines are not necessarily stable, so the cluster's DNS service will update the DNS records managed by DigitalOcean to the new IP as needed. @@ -75,4 +75,4 @@ The IPs of the DigitalOcean machines are not necessarily stable, so the cluster' ## Deploy -Yeah, you're done here. Back to [Deployment with Helm for Kubernetes](deployment/kubernetes/README.md). +Yeah, you're done here. Back to [Deployment with Helm for Kubernetes](/deployment/kubernetes/README.md). From 0dc321cf70227e7fd6da75177fad1950f874f9b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wolfgang=20Hu=C3=9F?= Date: Tue, 28 Sep 2021 09:57:20 +0200 Subject: [PATCH 2/3] Add the need of a Docker organisation --- deployment/kubernetes/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/deployment/kubernetes/README.md b/deployment/kubernetes/README.md index 18baa43..c528858 100644 --- a/deployment/kubernetes/README.md +++ b/deployment/kubernetes/README.md @@ -157,6 +157,8 @@ $ helm --kubeconfig=/../kubeconfig.yaml install dns bitnami/external-dns -f dns. ### Ocelot.Social +***Caution:** Before installing your own ocelot.social network, you need to create a DockerHub (account and) organization, put its name in the `package.json` file, and push your deployment and rebranding code to GitHub so that GitHub Actions can push your Docker images to DockerHub. This is because Kubernetes will pull these images to create PODs from them.* + All commands for ocelot need to be executed in the kubernetes folder. Therefore `cd deployment/kubernetes/` is expected to be run before every command. Furthermore the given commands will install ocelot into the default namespace. This can be modified to by attaching `--namespace not.default`. #### Install From ed76d712ddc8e11b5a9692a6dd5ed3e6f2656f7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wolfgang=20Hu=C3=9F?= Date: Tue, 28 Sep 2021 09:59:19 +0200 Subject: [PATCH 3/3] Change caution to attention --- deployment/kubernetes/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deployment/kubernetes/README.md b/deployment/kubernetes/README.md index c528858..410910e 100644 --- a/deployment/kubernetes/README.md +++ b/deployment/kubernetes/README.md @@ -157,7 +157,7 @@ $ helm --kubeconfig=/../kubeconfig.yaml install dns bitnami/external-dns -f dns. ### Ocelot.Social -***Caution:** Before installing your own ocelot.social network, you need to create a DockerHub (account and) organization, put its name in the `package.json` file, and push your deployment and rebranding code to GitHub so that GitHub Actions can push your Docker images to DockerHub. This is because Kubernetes will pull these images to create PODs from them.* +***Attention:** Before installing your own ocelot.social network, you need to create a DockerHub (account and) organization, put its name in the `package.json` file, and push your deployment and rebranding code to GitHub so that GitHub Actions can push your Docker images to DockerHub. This is because Kubernetes will pull these images to create PODs from them.* All commands for ocelot need to be executed in the kubernetes folder. Therefore `cd deployment/kubernetes/` is expected to be run before every command. Furthermore the given commands will install ocelot into the default namespace. This can be modified to by attaching `--namespace not.default`.