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

Setting to disable container-updates on specific hosts #967

Open
maxulm opened this issue Oct 23, 2024 · 6 comments
Open

Setting to disable container-updates on specific hosts #967

maxulm opened this issue Oct 23, 2024 · 6 comments
Labels
C-feature request New feature request

Comments

@maxulm
Copy link

maxulm commented Oct 23, 2024

I want to suggest a new step

  • Which tool is this about? Where is its repository?
  • Which operating systems are supported by this tool?
  • What should Topgrade do to figure out if the tool needs to be invoked?
  • Which exact commands should Topgrade run?
  • Does it have a --dry-run option? i.e., print what should be done and exit
  • Does it need the user to confirm the execution? And does it provide a --yes
    option to skip this step?

I want to suggest some general feature

Topgrade should be able to disable container-updates on a specific host

More information

@maxulm maxulm added the C-feature request New feature request label Oct 23, 2024
@SteveLauC
Copy link
Member

I am not quite sure I understand this feature, would you like to elaborate a bit? What's Topgrade's current behavior?

@maxulm
Copy link
Author

maxulm commented Oct 24, 2024

I have several servers automatically updated with topgrade.
On some of them, I don't want docker-containers to be updated automatically on others it should be done.
It's a bit difficult to explain. Hope you got it.

@SteveLauC
Copy link
Member

Ok, I get it. Currently, you have to configure your servers separately, on the servers where you don't want Docker/Podman images to be updated, disable the containers step.

@maxulm
Copy link
Author

maxulm commented Oct 24, 2024

So topgrade has a local config on the "slaves" and not just the config on the "master"?

@SteveLauC
Copy link
Member

So topgrade has a local config on the "slaves" and not just the config on the "master"?

True, every node should have its own configuration file or the default configuration will be used. The only thing that Topgrade's remote functionality will do is launch a Topgrade process on the remote node. And, Topgrade does not have a concept of cluster, they are all equivalent nodes.

@maxulm
Copy link
Author

maxulm commented Oct 24, 2024 via email

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

No branches or pull requests

2 participants