Enable TLS on Ingress Controller using Cert Manager / Let's Encrypt #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 25, 2023
emmastephenson
requested changes
Aug 25, 2023
emmastephenson
approved these changes
Aug 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves https://app.zenhub.com/workspaces/secret-6480bf2ee530095ab41ebbe9/issues/gh/cdcgov/phdi/779
This enables HTTPS on our Application Gateway Ingress Controller. Followed this guide from Azure.
Basically, added a helm release for cert manager, and a custom manifest for a ClusterIssuer resource, along with the Ingress we have set up in this PR in phdi-charts.
Had to use the gavinbunney/kubectl terraform provider instead of the official kubernetes provider because of this issue.
Also made a few cleanup changes on the deployment workflow.