staging: Add access to elastic scheduler rpc

Refs. swh/infra/sysadm-environment#5035

data/common/common.yaml

@@ -864,6 +864,10 @@ letsencrypt::certificates:
   software-stories_staging:
     domains:
       - software-stories.staging.swh.network
+  scheduler_staging:
+    domains:
+      - scheduler.staging.swh.network
+      - scheduler.internal.staging.swh.network
   graphql_staging:
     domains:
       - graphql.staging.swh.network
@@ -1257,6 +1261,10 @@ bind::resource_records:
     type: CNAME
     record: storage-cassandra.internal.staging.swh.network
     data: k8s-archive-staging-rke2.internal.staging.swh.network.
+  scheduler-staging/CNAME:
+    type: CNAME
+    record: scheduler.internal.staging.swh.network
+    data: k8s-archive-staging-rke2.internal.staging.swh.network.
   webapp-next-version-staging/CNAME:
     type: CNAME
     record: webapp-cassandra-next-version.internal.staging.swh.network

data/deployments/staging/common.yaml

@@ -149,6 +149,7 @@ swh::deploy::reverse_proxy::services:
   - objstorage
   - graphql
   - software-stories
+  - scheduler
 
 swh::postgresql::version: '12'
 swh::postgresql::port: 5433
@@ -374,3 +375,10 @@ cassandra::disable_stcs_in_l0: true
 swh::deploy::software-stories::reverse_proxy::backend_http_host: software-stories.internal.staging.swh.network
 swh::deploy::software-stories::base_url: software-stories.staging.swh.network
 swh::deploy::software-stories::vhost::letsencrypt_cert: software-stories_staging
+
+# scheduler within elastic infra
+swh::deploy::scheduler::reverse_proxy::backend_http_host: scheduler.internal.staging.swh.network
+swh::deploy::scheduler::reverse_proxy::backend_http_port: "80"
+swh::deploy::scheduler::base_url: scheduler.staging.swh.network
+swh::deploy::scheduler::vhost::letsencrypt_cert: scheduler_staging
+swh::deploy::scheduler::icinga_check_string: 'scheduler RPC server'