Add HTTPS Certificate to prombench.prometheus.io #777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #724
This PR aims to add an HTTPS certificate for
prombench.prometheus.io
using Cert-Manager and Let's Encrypt. Testing the setup locally has proven challenging. Here’s a summary of the modifications and approaches tried so far:Service
type toNodePort
fromLoadBalancer
for easier local access.Service
type toClusterIP
with Ingress managing external access.prombench-prometheus-tls
secret for HTTPS./etc/hosts
to mapprombench.prometheus.io
to127.0.0.1
but it worked when I mapped it to Node IP and add the Host in the header when testing to/etc/hosts
, but the challenge does not get solved automatically with the manifest setup.I’d appreciate any guidance on how to test this locally. The Issue was because of DNS since after mapping in
/etc/hosts
I was able to solve the challenge(Tested via curl)If there's a better way to test this locally. Please let me know.
Thank you!