Deploying Sametime
This section provides information to deploy Sametime to Kubernetes cluster.
Procedure
-
Deploy the helm chart.
helm install sametime .
Note:- The command assumes you are in the helm directory. The
.
represents current directory. - Instead of
sametime
you can choose any descriptive name for the deployment. You can also deploy the application in a namespace through the-n or --namespace
option. First create the namespace usingkubectl create namespace
.
If there are any errors, you must remove the installed product and fix the error before trying the installation again. To uninstall the product, run the following commands:# helm uninstall sametime
# kubectl delete job sametime
# kubectl delete clusterrolebinding sametime
# kubectl delete clusterrole sametime
# kubectl delete serviceaccount sametime
- The command assumes you are in the helm directory. The
-
For traffic to flow through the Ingress controller, you must apply a configuration map
to Ingress.
Create a file called mux-configmap.yaml with the following content.
apiVersion: v1 kind: ConfigMap metadata: name: tcp-services namespace: ingress-nginx data: 1533: "default/mux:mux"
-
Apply the configMap values to the configuration by running the following command.
kubectl apply -f mux-configmap.yaml
-
Run the following kubectl patch command so that port 1533 is
available.
kubectl -n ingress-nginx patch deployment ingress-nginx-controller --type=json -p='[\{"op": "replace", "path": "/spec/template/spec/containers/0/args", "value": ["/nginx-ingress-controller","--publish-service=$(POD_NAMESPACE)/ingress-nginx-controller","--election-id=ingress-controller-leader","--controller-class=k8s.io/ingress-nginx","--configmap=$(POD_NAMESPACE)/ingress-nginx-controller","--tcp-services-configmap=$(POD_NAMESPACE)/tcp-services"] }]'