initial acm config

tmp/acm-hub-bootstrap/overrides/values-AWS.yaml

@@ -0,0 +1,26 @@
+# The following snippet can be commented out in oroder
+# to enable letsencrypt certificates on API endpoint and default
+# ingress of the cluster
+# It is currently very experimental and unsupported.
+# PLEASE read https://github.com/hybrid-cloud-patterns/common/tree/main/letsencrypt#readme
+# for all the limitations around it
+
+
+# letsencrypt:
+#   enabled: true
+#   api_endpoint: true
+#   # FIXME: tweak this to match your region
+#   region: eu-central-1
+#   server: https://acme-v02.api.letsencrypt.org/directory
+#   # server: https://acme-staging-v02.api.letsencrypt.org/directory
+#   # FIXME: set this to your correct email
+#   email: iwashere@iwashere.com
+#
+# clusterGroup:
+#   applications:
+#     letsencrypt:
+#       name: letsencrypt
+#       namespace: letsencrypt
+#       # Using 'default' as that exists everywhere
+#       project: default
+#       path: common/letsencrypt

tmp/acm-hub-bootstrap/overrides/values-IBMCloud.yaml

@@ -0,0 +1,10 @@
+# When using IBM ROKS the route certificates are signed by letsencrypt
+# By default the ESO configuration uses the kube-root-ca.crt configmap
+# to validate the connection to vault. Since this configmap will not contain
+# the letsencrypt CA, ESO will be unable to connect to the vault and return an
+# x509 CA unknown error.
+# Uncomment the following if you are using IBM ROKS (IPI installs on IBM Cloud are unaffected)
+
+# golangExternalSecrets:
+#   caProvider:
+#     enabled: false