feat: use Acme Lets Encrypt cluster issuer for TLS in Hedera Explorer

[jeromy-cannon]

Description

This pull request changes the following:

• use Acme Lets Encrypt cluster issuer for TLS in Hedera Explorer

Related Issues

• Closes ChartTLS: TLS with Let's Encrypt for Hedera Mirror Node Explorer #631

[github-actions]

Unit Test Results

  26 files  ±0    26 suites  ±0   58s ⏱️ +2s
109 tests ±0  105 ✔️ ±0  4 💤 ±0  0 ❌ ±0 
110 runs  ±0  106 ✔️ ±0  4 💤 ±0  0 ❌ ±0 

Results for commit 99254a7. ± Comparison against base commit e44e5b2.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e44e5b2) 67.51% compared to head (99254a7) 67.51%.

Additional details and impacted files

@@            Coverage Diff            @@
##               main     #677   +/-   ##
=========================================
  Coverage     67.51%   67.51%           
  Complexity      339      339           
=========================================
  Files            64       64           
  Lines          1336     1336           
  Branches        157      157           
=========================================
  Hits            902      902           
  Misses          371      371           
  Partials         63       63           

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[jeromy-cannon]

Capturing notes in case they are needed to run various scenarios later:
@leninmehedy , @nathanklick , @JeffreyDallas

kind delete clusters fst
fsnetman cluster create

#KIND cluster setup
helm install fullstack-cluster-setup  ./fullstack-cluster-setup \
--namespace fullstack-cluster-setup --create-namespace \
--set "cloud.certManager.enabled=true" \
--set "cloud.minio.enabled=true" \
--set "cert-manager.installCRDs=true" 

helm uninstall fullstack-cluster-setup -n fullstack-cluster-setup

#Kind local (with TLS)
helm install network-deployment ./fullstack-deployment \
--namespace custom-network-a1 --create-namespace \
--set "cloud.s3.enabled=false" \
--set "cloud.gcs.enabled=false" \
--set "telemetry.prometheus.svcMonitor.enabled=false" \
--set "cloud.selfSignedClusterIssuer.enabled=true" \
--set "hedera-explorer.ingress.enabled=true" \
--set "cloud.haproxyIngressController.enabled=true" 

#Kind local (noTLS)(
helm install network-deployment ./fullstack-deployment \
--namespace custom-network-a1 --create-namespace \
--set "cloud.s3.enabled=false" \
--set "cloud.gcs.enabled=false" \
--set "telemetry.prometheus.svcMonitor.enabled=false" 

helm uninstall network-deployment -n custom-network-a1


#GKE cluster setup
helm install fullstack-cluster-setup  ./fullstack-cluster-setup --namespace fst-user --create-namespace 

helm uninstall fullstack-cluster-setup -n fst-user

#GKE self-signed
helm install network-deployment ./fullstack-deployment \
--namespace custom-network-a1 --create-namespace \
--set "cloud.s3.enabled=false" \
--set "cloud.gcs.enabled=false" \
--set "telemetry.prometheus.svcMonitor.enabled=false" \
--set "cloud.selfSignedClusterIssuer.enabled=true" \
--set "cloud.haproxyIngressController.enabled=true" \
--set "global.ingressClassName=custom-network-a1-hedera-explorer-ingress-class" \
--set "hedera-explorer.ingress.enabled=true" \
--set "haproxy-ingress.controller.service.loadBalancerIP=34.41.195.144" \
--set-json 'hedera-explorer.ingress.hosts[0]={"host":"34.41.195.144.nip.io","paths":[{"path":"/","pathType":"Prefix"}]}' 

#GKE acme staging
helm install network-deployment ./fullstack-deployment \
--namespace custom-network-a1 --create-namespace \
--set "cloud.s3.enabled=false" \
--set "cloud.gcs.enabled=false" \
--set "cloud.acmeClusterIssuer.enabled=true" \
--set "telemetry.prometheus.svcMonitor.enabled=false" \
--set "cloud.haproxyIngressController.enabled=true" \
--set "hedera-explorer.ingress.enabled=true" \
--set "global.ingressClassName=custom-network-a1-hedera-explorer-ingress-class" \
--set "hedera-explorer.certClusterIssuerType=acme-staging" \
--set "haproxy-ingress.controller.service.loadBalancerIP=34.41.195.144" \
--set-json 'hedera-explorer.ingress.hosts[0]={"host":"34.41.195.144.nip.io","paths":[{"path":"/","pathType":"Prefix"}]}' 

helm uninstall network-deployment -n custom-network-a1

[leninmehedy]

Capturing notes in case they are needed to run various scenarios later:

Thanks @jeromy-cannon . We should start documenting in a bit more detail in Notion so that we can refer back to it easily and maintain it. We need to know what each scenario mean and why someone would use it (probably a simple system diagram explaining the components...). Later that could help us to write up proper docs for end user.

[swirlds-automation]

🎉 This PR is included in version 0.18.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[swirlds-automation]

🎉 This PR is included in version 0.18.0 🎉

The release is available on:

• npm package (@release-0.18.x dist-tag)
• GitHub release

Your semantic-release bot 📦🚀