![\"\"](\"https:\/\/i0.wp.com\/blog.mi.hdm-stuttgart.de\/wp-content\/uploads\/2019\/01\/Screen-Shot-2018-12-29-at-23.56.46.png?fit=621%2C1024&ssl=1\")
![\"\"](\"https:\/\/i2.wp.com\/blog.mi.hdm-stuttgart.de\/wp-content\/uploads\/2019\/01\/Screen-Shot-2018-12-29-at-23.58.05.png?fit=656%2C414&ssl=1\")
![\"\"](\"https:\/\/i2.wp.com\/blog.mi.hdm-stuttgart.de\/wp-content\/uploads\/2019\/01\/Screen-Shot-2018-12-30-at-00.06.53.png?fit=656%2C181&ssl=1\")
Step 2: IBM Cloud <\/h2>\n\n\n\nContainer Registry<\/h3>\n
A container registry serves as a central repository for docker images to make them accessible from anywhere. It also checks for security vulnerabilities and performs versioning.\nSince our goal is to deploy the backend image in a cluster, we have to store it in an appropriate registry. Our choice was the IBMCloud Container Registry<\/a>.<\/p>\nIn order to use the Container Registry of the IBMCloud, several requirements have to be fulfilled:<\/p>\n
\n- The
IBMCloud CLI<\/code><\/a> has been installed.<\/li>\n- The
Docker CLI<\/code><\/a> has been installed.<\/li>\n- The IBMCloud Container-Registry Plug-In was installed via the command line through
ibmcloud plugin install container-registry -r Bluemix<\/code>.<\/li>\n<\/ol>\nOnce the tools have been installed or the prerequisites have been met, the setup of the container registry can be started. The following steps are necessary for this:<\/p>\n
\n- Log in to your IBMCloud account:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud login -a<\/span> https:\/\/api.eu-de.bluemix.net<\/pre>\n\n\n\n\n- Choose a name for the namespace, and create that namespace:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cr namespace-add <my_namespace>\n\n#e.g. <my_namespace> will be replaced by 'system_engineering_radcup'<\/span><\/pre>\n\n\n\nOverview of the existing namespaces:\n<\/p>\n![\"Alt\"](\"https:\/\/blog.mi.hdm-stuttgart.de\/wp-content\/uploads\/2019\/01\/Bildschirmfoto-2018-12-27-um-00.48.31-1.png\" "\\"Namespace")
<\/figure>\nAfter the namespace has been created, images can be pushed into it:<\/p>\n
\n- Log your local Docker daemon into the IBM Cloud Container Registry:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cr login<\/pre>\n\n\n\n\n- Choose a repository and tag by which you can identify the image:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
docker tag <image_name> registry.eu-de.bluemix.net\/<my_namespace>\/<my_repository>:<my_tag>\n\n# e.g. <image_name> -> radcup_backend, <my_namespace> -> system_engineering_radcup, <\/span>\n# <my_repository> -> radcup_backend and <my_tag> -> 1<\/span><\/pre>\n\n\n\n\n- Push the image:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
docker push registry.eu-de.bluemix.net\/<my_namespace>\/<my_repository>:<my_tag>\n\n# e.g. <my_namespace> -> system_engineering_radcup, <\/span>\n# <my_repository> -> radcup_backend and <my_tag> -> 1<\/span><\/pre>\n\n\n\n\n- Verify that your image is in your private registry:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cr image-list\n\nREPOSITORY TAG DIGEST NAMENSBEREICH ERSTELLT GR\u00d6SSE Sicherheitsstatus \nregistry.eu-de.bluemix.net\/system_engineering_radcup\/radcup_backend 1.1.1-build.xxxxxxx 330xxxxxcb61 system_engineering_radcup 4 days ago 288 MB 0 Probleme <\/pre>\n\n\n\nContainer\/Kubernetes Service<\/h3>\n<\/div>\n\n\n\nObjective: Deploy the docker image stored in the Container Registry in a cluster and make it publicly available.<\/p>\n
In order to achieve this goal, we decided to use the IBMCloud Container Service. It is based on native Kubernetes<\/a> and offers the user not only the possibility to deploy images, but also to track their status via a web interface.<\/p>\n<\/div>\n\n\n\n![\"\"](\"https:\/\/i2.wp.com\/blog.mi.hdm-stuttgart.de\/wp-content\/uploads\/2019\/01\/overview.png?fit=656%2C249&ssl=1\")
Overview of current deployments<\/figcaption><\/figure><\/div>\n\n\n\nIn order to deploy images, a cluster must first be created. There are two ways to do this:<\/p>\n
\n- The IBMCloud web interface\n
\n- In the catalog, select the IBM Cloud Kubernetes Service option<\/li>\n
- Select a region where your cluster will be deployed<\/li>\n
- Select the free cluster plan<\/li>\n
- Give your cluster a name<\/li>\n
- Click Set Up Cluster<\/li>\n<\/ul>\n<\/li>\n
- The IBMCLoud CLI<\/a><\/li>\n<\/ul>\n
If the cluster is to be created by using the CLI, the following steps are necessary:<\/p>\n
\n- Log in to your IBMCloud account:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud login -a<\/span> https:\/\/api.eu-de.bluemix.net<\/pre>\n\n\n\n\n- Install the IBMCloud Container Service Plug-In:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud plugin install container-service -r Bluemix<\/pre>\n\n\n\n\n- Create the cluster (this takes several minutes):<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud ks cluster-create --zone <my_zone> --name <my_cluster>\n# e.g. <my_zone> -> mil01,<\/span>\n# <my_cluster> -> radcup<\/span><\/pre>\n\n\n\n\n- Check whether the cluster was created successfully:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud ks clusters\n\nName ID Status Erstellt Worker Position Version Ressourcengruppenname \nradcup axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx normal 6 days ago 1 mil01 1.10.11_1536 Default \n<\/pre>\n\n\n\nOnce the cluster has been created, you can continue with the deployment of the images.<\/p>\n
\nFinding:<\/p>\n
In order to deploy the image, an image PullSecret must be created for the container registry. If this is not available and a deployment takes place, an error will appear in the web interface of the cluster because the cluster lacks the authorization to pull the needed image.<\/p>\n
\n- Create the token:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cr token-add --description \"radcup\"<\/span> --non-expiring --readwrite<\/pre>\n\n\n\n\n- Check whether the token was created:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cr token-list\n\nTOKEN-ID SCHREIBGESCH\u00dcTZT ABLAUF BESCHREIBUNG \nc192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx true 0 radcup <\/pre>\n\n\n\n\n- Get the value for your token:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cr token-get <token-id>\n\n# e.g. <token-id> -> c192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx<\/span>\n\nRegistry-Token mit eindeutiger Kennung 'c192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx'<\/span> wird abgerufen...\n \nToken-ID c192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx \nToken value of the token\n<\/pre>\n\n\n\n\n- Create the secret Kubernetes key to store your token information:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
kubectl --namespace <kubernetes-namespace> create secret docker-registry <name_of_the_secret_key> --docker-server=<registry-url> --docker-username=token --docker-password=<token_value> --docker-email=<docker-e<\/span>-mail>\n\n# e.g <kubernetes-namespace> -> default, <\/span>\n# <name_of_the_secret_key> -> radcup,<\/span>\n# <registry-url> -> registry.eu-de.bluemix.net,<\/span>\n# <token_value> -> value of the token (see above),<\/span>\n# <docker-e-mail> -> a@b.c<\/span><\/pre>\n\n\n\n\n- Check that the secret key was successfully created:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
kubectl get secrets --namespace <kubernetes-namespace>\n\n# e.g. <kubernetes-namespace> -> default<\/span>\n# Attention: For this to work, you must first 'log in' to the cluster. Otherwise you will get an error.<\/span>\n\nNAME TYPE DATA AGE\nradcup-hdm kubernetes.io\/dockerconfigjson 1 13d<\/pre>\n\n\n\n
\nTwo yaml files were defined in order to deploy the image stored in the container registry in the cluster and to make it accessible from outside:<\/p>\n
\n- \n
web-controller.yaml<\/p>\n
\n- Notice:<\/strong>\n
\n- We create a ReplicationController called web-controller, and we tell it to create two replicas of the template section (Pod configuration). The pod itself points to the container registry to load our image from there (please also see the imagePullSecrets section).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div>\n\n\n\n
# web-controller.yaml<\/span>\napiVersion:<\/span> v1\nkind:<\/span> ReplicationController\nmetadata:<\/span>\n labels:<\/span>\n name:<\/span> web\n name:<\/span> web-controller-version-radcup\nspec:<\/span>\n replicas:<\/span> 2<\/span>\n selector:<\/span>\n app:<\/span> radcup-backend\n version:<\/span> version-radcup\n template:<\/span>\n metadata:<\/span>\n labels:<\/span>\n name:<\/span> web\n app:<\/span> radcup-backend\n version:<\/span> version-radcup\n spec:<\/span>\n containers:<\/span>\n - image:<\/span> registry.eu-de.bluemix.net\/system_engineering_radcup\/radcup_backend:version-radcup\n name:<\/span> web\n command:<\/span> [\"bash\"<\/span>, \"-c\"<\/span>]\n args:<\/span> [\"npm run testfromclusterandrun\"<\/span>]\n env:<\/span>\n - name:<\/span> NODE_ENV\n value:<\/span> \"testDBatlas\"<\/span>\n ports:<\/span>\n - containerPort:<\/span> 3000<\/span>\n name:<\/span> http-server\n imagePullSecrets:<\/span>\n - name:<\/span> radcup-hdm\n restartPolicy:<\/span> Always\n<\/pre>\n\n\n\n
\nAdjustments in the course of the project:<\/em><\/p>\n\n- \n
labels<\/code>: are key-value pairs which are attached to pods, replication controller and services. They are used as identifying attributes for objects such as pods and replication controller.<\/p>\n<\/li>\n- \n
command and args<\/code>: starts the server in the container. Without these two lines, the Pod started, but then crashed immediately.<\/p>\n<\/li>\n- \n
version<\/code>: Uniquely identifies the deployment. Required to be able to perform a rolling update.<\/p>\n<\/li>\n<\/ul>\nIn addition, the name of the replication controller has been extended so that it can be adapted more easily before a rolling update (keyword: uniqueness).<\/p>\n
\n<\/div>\n\n\n\n\n- \n
web-service.yaml<\/p>\n
\n- Notice:<\/strong>\n
\n- We expose the service on port 80 internally within the cluster. That is, the service becomes visible on this port, and will send requests made to this port to the pods selected by the service. The TargetPort 3000 is the port on the pod that the requests gets sent to in this case.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div>\n\n\n\n
# web-service.yaml<\/span>\napiVersion:<\/span> v1\nkind:<\/span> Service\nmetadata:<\/span>\n name:<\/span> web\n labels:<\/span>\n name:<\/span> web\nspec:<\/span>\n type:<\/span> NodePort\n ports:<\/span>\n - port:<\/span> 80<\/span>\n targetPort:<\/span> 3000<\/span>\n protocol:<\/span> TCP\n selector:<\/span>\n name:<\/span> web<\/pre>\n\n\n\n
\nAdjustments in the course of the project:<\/em><\/p>\n\nselector<\/code>: Used to select a set of objects. Without the selector, there was no connection between the controller and the service (so no access was possible). Therefore, it had to be added with the appropriate key.<\/li>\n<\/ul>\n
\nNow the ReplicationController and the service can be created. Several steps are also necessary for this:<\/p>\n
\n- Log in to your IBM Cloud account:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud login -a<\/span> https:\/\/api.eu-de.bluemix.net<\/pre>\n\n\n\n\n- Target the IBM Cloud Container Service region in which you want to work:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cs region-set eu-central<\/pre>\n\n\n\n\n- Get the command to set the environment variable and download the Kubernetes configuration files:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
ibmcloud cs cluster-config <my_cluster>\n# e.g. <my_cluster> -> radcup<\/span><\/pre>\n\n\n\n\n- Set the KUBECONFIG environment variable. Copy the output from the previous command and paste it in your terminal:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
# The command output should look similar to the following command<\/span>\nexport<\/span> KUBECONFIG=\/Users\/$USER<\/span>\/.bluemix\/plugins\/container-service\/clusters\/<my_cluster>\/kube-config-<my_zone>-radcup.yml\n# e.g. <my_cluster> -> radcup,<\/span>\n# <my_zone> -> mil01<\/span><\/pre>\n\n\n\n\n- Verify that you can connect to your cluster by listing your worker nodes:<\/li>\n<\/ul>\n<\/div>\n\n\n\n
kubectl get nodes\n\nNAME STATUS ROLES AGE VERSION\n10.144.xxx.xxx Ready <none> 6d v1.10.11+IKS<\/pre>\n\n\n\nThe ReplicationController and the service can be created as follows:<\/p>\n<\/div>\n\n\n\n
kubectl create -f<\/span> web-controller.yaml\n\nkubectl create -f<\/span> web-service.yaml<\/pre>\n\n\n\nAfter executing the commands, the image is deployed and retrievable.<\/p>\n
\nFinding:<\/p>\n
Since the public IP address of the cluster and the port under which the service can be accessed are not directly known, the backend could not be accessed directly. Therefore, these had to be found out accordingly.<\/p>\n
Cluster-IP:<\/p>\n<\/div>\n\n\n\n
ibmcloud ks workers <cluster_name>\n\n# e.g. <cluster_name> -> radcup<\/span>\n\nID \u00d6ffentliche IP Private IP Maschinentyp Status Status Zone Version \nkube-mil01-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 159.122.181.248 10.xxx.xxx.xxx free normal Ready mil01 1.10.11_1537<\/pre>\n\n\n\nService-Port:<\/p>\n<\/div>\n\n\n\n
kubectl describe service <service_name>\n\n# e.g. <service_name> -> web<\/span>\n\nName: web\nNamespace: default\nLabels: name=web\n...\nSelector: name=web\nType: NodePort\n...\nPort: <unset<\/span>> 80\/TCP\nTargetPort: 3000\/TCP\nNodePort: <unset<\/span>> 30304\/TCP\n...<\/pre>\n\n\n\nAccordingly, the radcup backend would be accessible under http:\/\/159.122.181.248:30304\/api, for example.<\/p>\n
\n<\/div>\n\n\n\nKubernetes Load Balancing<\/h3>\n<\/div>\n\n\n\nProblem: If the utilization of a Pod is too high, not all requests arrive and the availability of the backend will decrease.<\/p>\n
One possible solution is the Horizontal Pod Autoscaler (HPA)<\/a> from Kubernetes.The HPA automatically scales the number of pods in a replication controller, deployment or replica set based on observed CPU usage or other metrics.<\/p>\n<\/div>\n\n\n\n
Container Registry<\/h3>\n
A container registry serves as a central repository for docker images to make them accessible from anywhere. It also checks for security vulnerabilities and performs versioning.\nSince our goal is to deploy the backend image in a cluster, we have to store it in an appropriate registry. Our choice was the IBMCloud Container Registry<\/a>.<\/p>\n In order to use the Container Registry of the IBMCloud, several requirements have to be fulfilled:<\/p>\n Once the tools have been installed or the prerequisites have been met, the setup of the container registry can be started. The following steps are necessary for this:<\/p>\n Overview of the existing namespaces:\n<\/p>\n After the namespace has been created, images can be pushed into it:<\/p>\n Objective: Deploy the docker image stored in the Container Registry in a cluster and make it publicly available.<\/p>\n In order to achieve this goal, we decided to use the IBMCloud Container Service. It is based on native Kubernetes<\/a> and offers the user not only the possibility to deploy images, but also to track their status via a web interface.<\/p>\n<\/div>\n\n\n\n In order to deploy images, a cluster must first be created. There are two ways to do this:<\/p>\n If the cluster is to be created by using the CLI, the following steps are necessary:<\/p>\n Once the cluster has been created, you can continue with the deployment of the images.<\/p>\n Finding:<\/p>\n In order to deploy the image, an image PullSecret must be created for the container registry. If this is not available and a deployment takes place, an error will appear in the web interface of the cluster because the cluster lacks the authorization to pull the needed image.<\/p>\n Two yaml files were defined in order to deploy the image stored in the container registry in the cluster and to make it accessible from outside:<\/p>\n web-controller.yaml<\/p>\n Adjustments in the course of the project:<\/em><\/p>\n In addition, the name of the replication controller has been extended so that it can be adapted more easily before a rolling update (keyword: uniqueness).<\/p>\n web-service.yaml<\/p>\n Adjustments in the course of the project:<\/em><\/p>\n Now the ReplicationController and the service can be created. Several steps are also necessary for this:<\/p>\n The ReplicationController and the service can be created as follows:<\/p>\n<\/div>\n\n\n\n After executing the commands, the image is deployed and retrievable.<\/p>\n Finding:<\/p>\n Since the public IP address of the cluster and the port under which the service can be accessed are not directly known, the backend could not be accessed directly. Therefore, these had to be found out accordingly.<\/p>\n Cluster-IP:<\/p>\n<\/div>\n\n\n\n Service-Port:<\/p>\n<\/div>\n\n\n\n Accordingly, the radcup backend would be accessible under http:\/\/159.122.181.248:30304\/api, for example.<\/p>\n Problem: If the utilization of a Pod is too high, not all requests arrive and the availability of the backend will decrease.<\/p>\n One possible solution is the Horizontal Pod Autoscaler (HPA)<\/a> from Kubernetes.The HPA automatically scales the number of pods in a replication controller, deployment or replica set based on observed CPU usage or other metrics.<\/p>\n<\/div>\n\n\n\n\n
IBMCloud CLI<\/code><\/a> has been installed.<\/li>\nDocker CLI<\/code><\/a> has been installed.<\/li>\nibmcloud plugin install container-registry -r Bluemix<\/code>.<\/li>\n<\/ol>\n\n
ibmcloud login -a<\/span> https:\/\/api.eu-de.bluemix.net<\/pre>\n\n\n\n\n
ibmcloud cr namespace-add <my_namespace>\n\n#e.g. <my_namespace> will be replaced by 'system_engineering_radcup'<\/span><\/pre>\n\n\n\n<\/figure>\n\n
ibmcloud cr login<\/pre>\n\n\n\n
\n
docker tag <image_name> registry.eu-de.bluemix.net\/<my_namespace>\/<my_repository>:<my_tag>\n\n# e.g. <image_name> -> radcup_backend, <my_namespace> -> system_engineering_radcup, <\/span>\n# <my_repository> -> radcup_backend and <my_tag> -> 1<\/span><\/pre>\n\n\n\n\n
docker push registry.eu-de.bluemix.net\/<my_namespace>\/<my_repository>:<my_tag>\n\n# e.g. <my_namespace> -> system_engineering_radcup, <\/span>\n# <my_repository> -> radcup_backend and <my_tag> -> 1<\/span><\/pre>\n\n\n\n\n
ibmcloud cr image-list\n\nREPOSITORY TAG DIGEST NAMENSBEREICH ERSTELLT GR\u00d6SSE Sicherheitsstatus \nregistry.eu-de.bluemix.net\/system_engineering_radcup\/radcup_backend 1.1.1-build.xxxxxxx 330xxxxxcb61 system_engineering_radcup 4 days ago 288 MB 0 Probleme <\/pre>\n\n\n\n
Container\/Kubernetes Service<\/h3>\n<\/div>\n\n\n\n
\n
\n
\n
ibmcloud login -a<\/span> https:\/\/api.eu-de.bluemix.net<\/pre>\n\n\n\n\n
ibmcloud plugin install container-service -r Bluemix<\/pre>\n\n\n\n
\n
ibmcloud ks cluster-create --zone <my_zone> --name <my_cluster>\n# e.g. <my_zone> -> mil01,<\/span>\n# <my_cluster> -> radcup<\/span><\/pre>\n\n\n\n\n
ibmcloud ks clusters\n\nName ID Status Erstellt Worker Position Version Ressourcengruppenname \nradcup axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx normal 6 days ago 1 mil01 1.10.11_1536 Default \n<\/pre>\n\n\n\n
\n\n
ibmcloud cr token-add --description \"radcup\"<\/span> --non-expiring --readwrite<\/pre>\n\n\n\n\n
ibmcloud cr token-list\n\nTOKEN-ID SCHREIBGESCH\u00dcTZT ABLAUF BESCHREIBUNG \nc192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx true 0 radcup <\/pre>\n\n\n\n
\n
ibmcloud cr token-get <token-id>\n\n# e.g. <token-id> -> c192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx<\/span>\n\nRegistry-Token mit eindeutiger Kennung 'c192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx'<\/span> wird abgerufen...\n \nToken-ID c192f4ad-xxxx-5208-98e4-xxxxxxxxxxxx \nToken value of the token\n<\/pre>\n\n\n\n\n
kubectl --namespace <kubernetes-namespace> create secret docker-registry <name_of_the_secret_key> --docker-server=<registry-url> --docker-username=token --docker-password=<token_value> --docker-email=<docker-e<\/span>-mail>\n\n# e.g <kubernetes-namespace> -> default, <\/span>\n# <name_of_the_secret_key> -> radcup,<\/span>\n# <registry-url> -> registry.eu-de.bluemix.net,<\/span>\n# <token_value> -> value of the token (see above),<\/span>\n# <docker-e-mail> -> a@b.c<\/span><\/pre>\n\n\n\n\n
kubectl get secrets --namespace <kubernetes-namespace>\n\n# e.g. <kubernetes-namespace> -> default<\/span>\n# Attention: For this to work, you must first 'log in' to the cluster. Otherwise you will get an error.<\/span>\n\nNAME TYPE DATA AGE\nradcup-hdm kubernetes.io\/dockerconfigjson 1 13d<\/pre>\n\n\n\n
\n\n
\n
\n
# web-controller.yaml<\/span>\napiVersion:<\/span> v1\nkind:<\/span> ReplicationController\nmetadata:<\/span>\n labels:<\/span>\n name:<\/span> web\n name:<\/span> web-controller-version-radcup\nspec:<\/span>\n replicas:<\/span> 2<\/span>\n selector:<\/span>\n app:<\/span> radcup-backend\n version:<\/span> version-radcup\n template:<\/span>\n metadata:<\/span>\n labels:<\/span>\n name:<\/span> web\n app:<\/span> radcup-backend\n version:<\/span> version-radcup\n spec:<\/span>\n containers:<\/span>\n - image:<\/span> registry.eu-de.bluemix.net\/system_engineering_radcup\/radcup_backend:version-radcup\n name:<\/span> web\n command:<\/span> [\"bash\"<\/span>, \"-c\"<\/span>]\n args:<\/span> [\"npm run testfromclusterandrun\"<\/span>]\n env:<\/span>\n - name:<\/span> NODE_ENV\n value:<\/span> \"testDBatlas\"<\/span>\n ports:<\/span>\n - containerPort:<\/span> 3000<\/span>\n name:<\/span> http-server\n imagePullSecrets:<\/span>\n - name:<\/span> radcup-hdm\n restartPolicy:<\/span> Always\n<\/pre>\n\n\n\n
\n\n
labels<\/code>: are key-value pairs which are attached to pods, replication controller and services. They are used as identifying attributes for objects such as pods and replication controller.<\/p>\n<\/li>\ncommand and args<\/code>: starts the server in the container. Without these two lines, the Pod started, but then crashed immediately.<\/p>\n<\/li>\nversion<\/code>: Uniquely identifies the deployment. Required to be able to perform a rolling update.<\/p>\n<\/li>\n<\/ul>\n
\n<\/div>\n\n\n\n\n
\n
\n
# web-service.yaml<\/span>\napiVersion:<\/span> v1\nkind:<\/span> Service\nmetadata:<\/span>\n name:<\/span> web\n labels:<\/span>\n name:<\/span> web\nspec:<\/span>\n type:<\/span> NodePort\n ports:<\/span>\n - port:<\/span> 80<\/span>\n targetPort:<\/span> 3000<\/span>\n protocol:<\/span> TCP\n selector:<\/span>\n name:<\/span> web<\/pre>\n\n\n\n
\n\n
selector<\/code>: Used to select a set of objects. Without the selector, there was no connection between the controller and the service (so no access was possible). Therefore, it had to be added with the appropriate key.<\/li>\n<\/ul>\n
\n\n
ibmcloud login -a<\/span> https:\/\/api.eu-de.bluemix.net<\/pre>\n\n\n\n\n
ibmcloud cs region-set eu-central<\/pre>\n\n\n\n
\n
ibmcloud cs cluster-config <my_cluster>\n# e.g. <my_cluster> -> radcup<\/span><\/pre>\n\n\n\n\n
# The command output should look similar to the following command<\/span>\nexport<\/span> KUBECONFIG=\/Users\/$USER<\/span>\/.bluemix\/plugins\/container-service\/clusters\/<my_cluster>\/kube-config-<my_zone>-radcup.yml\n# e.g. <my_cluster> -> radcup,<\/span>\n# <my_zone> -> mil01<\/span><\/pre>\n\n\n\n\n
kubectl get nodes\n\nNAME STATUS ROLES AGE VERSION\n10.144.xxx.xxx Ready <none> 6d v1.10.11+IKS<\/pre>\n\n\n\n
kubectl create -f<\/span> web-controller.yaml\n\nkubectl create -f<\/span> web-service.yaml<\/pre>\n\n\n\n
\nibmcloud ks workers <cluster_name>\n\n# e.g. <cluster_name> -> radcup<\/span>\n\nID \u00d6ffentliche IP Private IP Maschinentyp Status Status Zone Version \nkube-mil01-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 159.122.181.248 10.xxx.xxx.xxx free normal Ready mil01 1.10.11_1537<\/pre>\n\n\n\nkubectl describe service <service_name>\n\n# e.g. <service_name> -> web<\/span>\n\nName: web\nNamespace: default\nLabels: name=web\n...\nSelector: name=web\nType: NodePort\n...\nPort: <unset<\/span>> 80\/TCP\nTargetPort: 3000\/TCP\nNodePort: <unset<\/span>> 30304\/TCP\n...<\/pre>\n\n\n\n
\n<\/div>\n\n\n\nKubernetes Load Balancing<\/h3>\n<\/div>\n\n\n\n