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
Description:
Currently, reloader doesn't support CronJobs, so I have implemented support for Kubernetes CronJobs in the Stakater/Reloader repository and would like to contribute this feature back to the project.
Feature Implementation:
I have extended the functionality of Reloader to include support for Kubernetes CronJobs. With this enhancement, Reloader can now detect changes in ConfigMaps/Secrets and perform triggering a Job from an existing CronJob definition.
Steps to Reproduce:
To observe the added functionality, you can follow these steps:
Install Reloader in your Kubernetes cluster using the existing installation instructions.
Create a CronJob resource definition and add the annotations to watch for ConfigMaps/secrets.
Apply changes to the ConfigMap/Secrets resource such as modifying the data.
Verify that Reloader detects the changes and triggers a Job from the CronJob.
Code Contribution:
I have made the necessary modifications to the Reloader codebase to enable support for Kubernetes CronJobs. The changes include additions to the Reloader's resource detection logic and the implementation of triggering a Job from an existing CronJob.
I have thoroughly tested the feature, which works as expected in my company's pre-production environment.
I would happily contribute the code changes I've made to the Stakater/Reloader repository and collaborate with the maintainers to ensure proper integration.
If you think this feature is lacking and it's in your roadmap. Please let me know how I can proceed with this contribution.
The text was updated successfully, but these errors were encountered:
Description:
Currently, reloader doesn't support CronJobs, so I have implemented support for Kubernetes CronJobs in the Stakater/Reloader repository and would like to contribute this feature back to the project.
Feature Implementation:
I have extended the functionality of Reloader to include support for Kubernetes CronJobs. With this enhancement, Reloader can now detect changes in ConfigMaps/Secrets and perform triggering a Job from an existing CronJob definition.
Steps to Reproduce:
To observe the added functionality, you can follow these steps:
Install Reloader in your Kubernetes cluster using the existing installation instructions.
Create a CronJob resource definition and add the annotations to watch for ConfigMaps/secrets.
Apply changes to the ConfigMap/Secrets resource such as modifying the data.
Verify that Reloader detects the changes and triggers a Job from the CronJob.
Code Contribution:
I have made the necessary modifications to the Reloader codebase to enable support for Kubernetes CronJobs. The changes include additions to the Reloader's resource detection logic and the implementation of triggering a Job from an existing CronJob.
I have thoroughly tested the feature, which works as expected in my company's pre-production environment.
I would happily contribute the code changes I've made to the Stakater/Reloader repository and collaborate with the maintainers to ensure proper integration.
If you think this feature is lacking and it's in your roadmap. Please let me know how I can proceed with this contribution.
The text was updated successfully, but these errors were encountered: