Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

automatic security updates #1594

Open
ltalirz opened this issue Jun 7, 2023 · 1 comment
Open

automatic security updates #1594

ltalirz opened this issue Jun 7, 2023 · 1 comment
Labels
kind/feature New feature request

Comments

@ltalirz
Copy link
Contributor

ltalirz commented Jun 7, 2023

In what area(s)?

/area administration
/area ansible
/area autoscaling
/area configuration
/area cyclecloud
/area documentation
/area image
/area job-scheduling
/area monitoring
/area ood
/area remote-visualization
/area user-management

Describe the feature

Many playbooks currently contain a task

  - name: update packages for security
    become: true
    yum:
      name: '*'
      state: latest
      exclude: cyclecloud*

Not only does this task slow down the playbooks, it also does not keep the systems up to date when you are not running playbooks.

There are ansible roles for this, such as https://github.com/geerlingguy/ansible-role-security that will install cronjobs (yum-cron for rhel-based, unattended-upgrades for debian-based systems) that periodically install security patches (and only security patches) to keep the VMs up to date at all times.
I believe we should use them

@ltalirz ltalirz added the kind/feature New feature request label Jun 7, 2023
@xpillons
Copy link
Collaborator

xpillons commented Jun 8, 2023

I think it would probably be easier to do our own cron instead of relying on another repo. At the end it's just a cron running yum with security updates.
Best would be to rely on the azure platform for managing security update globally see #1413
issue with azure update is that it only support a specific list of marketplace images and not custom images

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature request
Projects
None yet
Development

No branches or pull requests

2 participants