Unable to join Slack - asking question here instead :/

[StFS]

Sorry if I'm misusing the GitHub issues here but I did try to join the Slack channel but just ended up in some login loop. It seems that my gmail email address is not allowed to join the Stakater Slack for whatever reason (I go to https://stakater.slack.com/ and click "Sign in with Google", choose my Gmail account but then just end up at https://stakater.slack.com/?sso_failed=1 with no explanation :/

But what I wanted to ask is this:

I have Reloader running on my k8s cluster and so far it's been running with the default settings (so using the env var reload strategy). But I want to switch over to the annotation reload strategy so I've re-deployed Reloader with the runtime argument that configures it to use the annotations reload strategy.

My question is how this will behave for already running resources (deployments, configmaps and secrets)? Will the Reloader operator pick up on changes to Secrets / ConfigMaps and reload the deployment (and use annotations from then on) or do I need to perform some extra steps to "reset" my cluster state so that Reloader will continue operating properly?

I ask because as I said, I re-deployed Reloader to my cluster and then I tried editing one of the secrets that a deployment is monitoring through Reloader. After editing the secret, the deployment did not get reloaded and I'm a bit confused about that.

Maybe reloader does not pick up on editing secrets / configmaps? Do I need to delete and re-create the secret / configmap?

Is there some magic kubectl command that would allow me to "kick" a configmap / secret to force Reloader to reload dependent components?

[MuneebAijaz]

hi @StFS i will check the stakater slack link and let you know when its fixed.

As for the other question, I actually tested it myself few days back using Reloader helm chart, I just changed the reload strategy and did a helm upgrade. It works as expected, and it reloads the deployments.
About the manual actions, there are none needed to switch to different reload strategy.

It actively keeps watching secrets and configmaps and processes over that. So the only action you would need is to change the contents of secret or configmap. (or creation/deletion in case of reloadOnCreate and reloadOnDelete).
Pls make sure all of your manifests are correct after the switch. If you can share them in this thread, i might be able to guide you in finding the problems.

Check for annotations on deployments/secrets/configmaps, values for reloader chart if deployed via chart, logs of reloader to see if it's watching in respective namespaces.

[MuneebAijaz]

Can you check if the invite works for you instead of Google SSO?

[StFS]

Can you check if the invite works for you instead of Google SSO?

Sorry, not sure what you mean here? You mean use the "I have a guest account" button instead of "Sign in with Google"?

I'm unable to do that because that asks me for a email and password (which I don't have). If I click the "forgot password" link I get an email stating "No account found".

If you are referring to something else, I'm afraid I don't understand what you mean. I don't seem to be able to request an invite in any way, at least not from that login page.

[MuneebAijaz]

I was referring to this field, if you enter your email here and click the link from your email, it should work.

[StFS]

I'm not seeing that screen. All I see is the following:

Can you send me the URL where you get this screen?

[StFS]

ahh... found it by googling: https://slack.stakater.com/

note that this is not the link that's in the GitHub readmy... that one is https://stakater.slack.com

[StFS]

woohoo... manged to get an invite from that link... so now I'm in 🕺

[StFS]

might be a good idea to have the link where you can get the invite on https://github.com/stakater/Reloader?tab=readme-ov-file#help ;)

[karl-johan-grahn]

Feel free to open a PR to update the readme 😄

[karl-johan-grahn]

And no worries about asking questions in GitHub, we monitor this more regularly every week

[MuneebAijaz]

hi @StFS was your main issue with Reloader was fixed?

[StFS]

@MuneebAijaz yes it was. Thank you!