Skip to content

force forward auth redeployment when tls secret changes - #2771

Draft
Adam-D-Lewis wants to merge 2 commits into
mainfrom
force_forward_auth_redeployment_with_new_tls_cert
Draft

force forward auth redeployment when tls secret changes#2771
Adam-D-Lewis wants to merge 2 commits into
mainfrom
force_forward_auth_redeployment_with_new_tls_cert

Conversation

@Adam-D-Lewis

@Adam-D-Lewis Adam-D-Lewis commented Oct 14, 2024

Copy link
Copy Markdown
Member

Reference Issues or PRs

I believe this will fix #2772, but I haven't tested it yet.

What does this implement/fix?

Put a x in the boxes that apply

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds a feature)
  • Breaking change (fix or feature that would cause existing features not to work as expected)
  • Documentation Update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Other (please describe):

Testing

  • Did you test the pull request locally?
  • Did you add new tests?

How to test this PR?

Any other comments?

Comment on lines +174 to 179
data "kubernetes_secret_v1" "cert_secret" {
metadata {
name = var.cert_secret_name
namespace = var.namespace
}
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if there is no secret available, will this block the deployment? considering backwards compatibility... maybe use a count

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New 🚦

Development

Successfully merging this pull request may close these issues.

[BUG] - Forwardauth pod not restarted when custom cert is updated

2 participants