--- title: Charmhub | Deploy MAAS Site Manager Operator for Kubernetes using Charmhub - The Open Operator Collection description: Deploy the latest version of MAAS Site Manager Operator for Kubernetes as a Kubernetes Operator on any cloud. url: https://charmhub.io/maas-site-manager-k8s/docs/t-deploy-temporal --- # MAAS Site Manager Operator for Kubernetes [MAAS Maintainers](https://charmhub.io/publisher/maas-maintainers "View all packages from MAAS Maintainers") * [MAAS Maintainers](https://charmhub.io/publisher/maas-maintainers "View all packages from MAAS Maintainers") Platform: 1.1/beta 53 ``` juju deploy maas-site-manager-k8s --channel 1.1/beta ``` [Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications) --- #### Relevant links * [Homepage](https://launchpad.net/maas-site-manager) --- #### Contacts * [Submit a bug](https://github.com/canonical/maas-site-manager-k8s-operator/issues) --- Share your thoughts on this charm with the community on discourse. [Join the discussion](https://discourse.charmhub.io/) # Deploy Temporal MAAS Site Manager uses Temporal Workflows for long-running tasks. Follow the steps below to deploy charmed Temporal. ## [Deploy Temporal Server](https://charmhub.io/maas-site-manager-k8s/docs/t-deploy-temporal#p-37779-deploy-temporal-server) First, add another Juju model for Temporal and deploy the Temporal charms: ``` juju add-model temporal juju deploy temporal-k8s --config num-history-shards=4 juju deploy temporal-admin-k8s juju deploy temporal-ui-k8s --config external-hostname=temporal-ui ``` Next, create relations for the Temporal charms: ``` juju consume admin/msm.pgsql juju relate temporal-k8s:db admin/msm.pgsql juju relate temporal-k8s:visibility admin/msm.pgsql juju relate temporal-k8s:admin temporal-admin-k8s:admin juju relate temporal-k8s:ui temporal-ui-k8s:ui ``` Once the charms have settled and are `active/idle`, create a Temporal namespace for MAAS Site Manager. Here, we use the name `msm-namespace`: ``` juju run temporal-admin-k8s/0 tctl args="--ns msm-namespace namespace register -rd 3" --wait 1m ``` ## [Deploy Ingress Controller](https://charmhub.io/maas-site-manager-k8s/docs/t-deploy-temporal#p-37779-deploy-ingress-controller) To enable TLS connections, you must have a TLS certificate stored as a k8s secret. You can create a self-signed certificate and store it in a secret as follows: ``` # Generate private key openssl genrsa -out server.key 2048 # Generate a certificate signing request openssl req -new -key server.key -out server.csr -subj "/CN=temporal" # Create self-signed certificate openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt -extfile <(printf "subjectAltName=DNS:temporal") # Create a k8s secret microk8s kubectl -n temporal create secret tls temporal-tls --cert=server.crt --key=server.key ``` Repeat this process for the Temporal UI: ``` # Generate private key openssl genrsa -out server.key 2048 # Generate a certificate signing request openssl req -new -key server.key -out server.csr -subj "/CN=temporal-ui" # Create self-signed certificate openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt -extfile <(printf "subjectAltName=DNS:temporal-ui") # Create a k8s secret microk8s kubectl -n temporal create secret tls temporal-ui-tls --cert=server.crt --key=server.key ``` Next, enable ingress and deploy two instances of `nginx-ingress-integrator` under the names `ingress` and `ingress-ui` and wait for them to enter an `waiting/idle` state: ``` sudo microk8s enable ingress juju deploy nginx-ingress-integrator ingress --channel edge --trust --config service-hostname=temporal --config tls-secret-name=temporal-tls juju deploy nginx-ingress-integrator ingress-ui --channel edge --trust --config service-hostname=temporal-ui --config tls-secret-name=temporal-ui-tls juju status --watch 5s ``` Next, relate `temporal-ui-k8s` and `temporal-k8s` to the respective `nginx-ingress-integrator` applications: ``` juju relate temporal-k8s ingress juju relate temporal-ui-k8s ingress-ui ``` Finally, configure the `tls-secret-name` for `temporal-k8s` and `temporal-ui-k8s`: ``` juju config temporal-k8s tls-secret-name=temporal-tls juju config temporal-ui-k8s tls-secret-name=temporal-ui-tls ``` To verify that ingress resources were created correctly, run the following command: ``` microk8s kubectl describe ingress -n temporal ``` You should see an output similar to below, with differing IP addresses: ``` Name: temporal-k8s-ingress Labels: app.juju.is/created-by=nginx-ingress-integrator nginx-ingress-integrator.charm.juju.is/managed-by=nginx-ingress-integrator Namespace: temporal-model Address: 127.0.0.1 Ingress Class: public Default backend: TLS: temporal-tls terminates temporal-k8s Rules: Host Path Backends ---- ---- -------- temporal-k8s / temporal-k8s-service:7233 (10.1.232.64:7233) Annotations: nginx.ingress.kubernetes.io/backend-protocol: GRPC nginx.ingress.kubernetes.io/proxy-body-size: 20m nginx.ingress.kubernetes.io/proxy-read-timeout: 60 nginx.ingress.kubernetes.io/rewrite-target: / Events: Name: temporal-ui-k8s-ingress Labels: app.juju.is/created-by=nginx-ingress-integrator nginx-ingress-integrator.charm.juju.is/managed-by=nginx-ingress-integrator Namespace: temporal-model Address: 127.0.0.1 Ingress Class: public Default backend: TLS: temporal-tls terminates temporal-ui-k8s Rules: Host Path Backends ---- ---- -------- temporal-ui-k8s / temporal-ui-k8s-service:8080 (10.1.232.72:8080) Annotations: nginx.ingress.kubernetes.io/backend-protocol: HTTP nginx.ingress.kubernetes.io/proxy-body-size: 20m nginx.ingress.kubernetes.io/proxy-read-timeout: 60 nginx.ingress.kubernetes.io/rewrite-target: / Events: ``` Note the IP address and port of the `temporal-k8s` service (in the output above, this is `10.1.232.64:7233`). **Next Step**: [Set up a reverse-proxy](https://charmhub.io/maas-site-manager-k8s/docs/t-reverse-proxy) ---