Skip to content

Conversation

@ankur512512
Copy link

@ankur512512 ankur512512 commented Jul 11, 2025

This will allow the reflection of middlemail-rabbitmq secret in other namespaces.

Please note that this annotation will not automatically create this secret in other namespaces but it will allow other namespaces to fetch the latest value from this secret using another annotation, whenever the source secret changes, using reflector operator.

@ahsan0608
Copy link

LGTM! Feel free to merge when you're ready!

@saraedum
Copy link
Member

Since this is a public repo, I think the setup here should not be that opinionated. Could we just pull in some annotations from the values instead? (Like all the bitnami charts do it? e.g., search for "annotations" here: https://github.com/bitnami/charts/tree/main/bitnami/postgresql#parameters)

@ankur512512
Copy link
Author

@saraedum yeah that makes sense, thanks for the review.

I have pushed the changes, please let me know if it looks good now.

@saraedum
Copy link
Member

This change goes in the right direction but I don't think it fixes the issue.

The helm hook annotations are not opinionated. They should be kept as they were. The other annotations should usually be redis.secret.annotations and rabbitmq.secret.annotations or something like that. However, they should be empty to give the user a way to inject their own annotations (and not put the opinionated reflector annotation there that is particular to your setup.)

@ankur512512
Copy link
Author

@saraedum Ah, okay. Got your point !!

Fixed it now.

P.S. I am only touching rabbitmq secret as of now because I need that one only for my setup.

@ankur512512
Copy link
Author

This change goes in the right direction but I don't think it fixes the issue.

The helm hook annotations are not opinionated. They should be kept as they were. The other annotations should usually be redis.secret.annotations and rabbitmq.secret.annotations or something like that. However, they should be empty to give the user a way to inject their own annotations (and not put the opinionated reflector annotation there that is particular to your setup.)

Hi, can you please review again and approve if you feel it looks okay.

@saraedum
Copy link
Member

I think you misunderstood my point here:

However, they should be empty to give the user a way to inject their own annotations (and not put the opinionated reflector annotation there that is particular to your setup.)

The values file should not ship such annotations. They are too opinionated to be in a chart that others might consider upstream.

@ankur512512
Copy link
Author

I think you misunderstood my point here:

However, they should be empty to give the user a way to inject their own annotations (and not put the opinionated reflector annotation there that is particular to your setup.)

The values file should not ship such annotations. They are too opinionated to be in a chart that others might consider upstream.

Sorry, I understood your point but I actually forgot to delete them before pushing after testing.
Should be good now. Let me know if it looks okay.

@saraedum
Copy link
Member

lgtm

@ankur512512 ankur512512 force-pushed the INFRA-189-patch-middlemail-helm-chart-to-allow-reflection-of-secrets branch from 59c86e7 to 13cb300 Compare July 21, 2025 10:09
@ankur512512 ankur512512 force-pushed the INFRA-189-patch-middlemail-helm-chart-to-allow-reflection-of-secrets branch from 13cb300 to 4998823 Compare July 21, 2025 10:11
@ankur512512
Copy link
Author

lgtm

Hi, could you please approve and merge? I don't have the permissions to do that.

@saraedum saraedum merged commit 8d298f3 into Miaplaza:master Jul 27, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants