You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The final thing we need to do is update our Mosquitto deployment with annotations that Reloader uses to redeploy pods when a specified configmap or secret changes.
Check out the Reloader docs for more info on how it works: Reloader
To track the configmap and secret resources of our Mosquitto pod we need to add the following annotations in the metadata section of the Mosquitto deployment.yaml:
Once you update the deployment.yaml manifest click save and finally we can check if our Reloader pod is working. At the web UI take a look at the secrets tab while in your Mosquitto project and select the mosquitto-secret-file resource. Take a look at the yaml of the secret resource and change the username or password to something else. As always click save to apply the changes. Now take a look back at your Reloader pod logs and you should see something like this:
The change was picked up by Reloader! if you look at the Mosquitto pod you'll see that it was just recreated to reflect the changes. This redeployment was triggered by Reloader!
You can also test that changes to the Mosquitto configmap by making a change to the configmap yaml like below:
Now looking back at the Reloader logs:
Reloader detected our configmap changes too! And there you have it. We have successfully configured and deployed 2 applications in our OpenShift cluster! Most basic application deployments will be spun up in a similar way, and you can take what you've seen here to help with debugging your next deployment.
The text was updated successfully, but these errors were encountered:
The final thing we need to do is update our Mosquitto deployment with annotations that Reloader uses to redeploy
pods
when a specifiedconfigmap
orsecret
changes.Check out the Reloader docs for more info on how it works: Reloader
To track the
configmap
andsecret
resources of our Mosquittopod
we need to add the following annotations in the metadata section of the Mosquitto deployment.yaml:deployment.yaml
Once you update the deployment.yaml manifest click save and finally we can check if our Reloader
pod
is working. At the web UI take a look at the secrets tab while in your Mosquitto project and select the mosquitto-secret-file resource. Take a look at the yaml of the secret resource and change the username or password to something else. As always click save to apply the changes. Now take a look back at your Reloader pod logs and you should see something like this:The change was picked up by Reloader! if you look at the Mosquitto
pod
you'll see that it was just recreated to reflect the changes. This redeployment was triggered by Reloader!You can also test that changes to the Mosquitto
configmap
by making a change to theconfigmap
yaml like below:Now looking back at the Reloader logs:
Reloader detected our
configmap
changes too! And there you have it. We have successfully configured and deployed 2 applications in our OpenShift cluster! Most basic application deployments will be spun up in a similar way, and you can take what you've seen here to help with debugging your next deployment.The text was updated successfully, but these errors were encountered: