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

Adopt Isolated Cluster creation to the new possibility of machine / firewall creation with DNS and NTP Servers #433

Open
3 tasks
majst01 opened this issue Nov 11, 2024 · 1 comment
Assignees

Comments

@majst01
Copy link
Contributor

majst01 commented Nov 11, 2024

Since metal-stack/metal-api#571 it is possible to specify DNS and NTP Servers during machine/firewall creation. This enables us to simplify the logic to modify the DNS and NTP Server configuration with the help of the os-metal-extension.

Instead we should adopt the machine/firewall creation process to put the DNS and NTP Servers given in the cloud profile for isolated clusters to the allocation.

This needs to be adopted in:

  • this repo
  • the os-metal-extension
  • machine-controller-manager-metal

If in a specific partition these parameters are defined, the parameters from the cloud profile must be of higher precedence.

@Gerrit91 @mwennrich @simcod @vknabel @robertvolkmann Please add comments if required.

@robertvolkmann
Copy link
Contributor

Please mind the documentation: https://github.com/metal-stack/docs/blob/master/docs/src/overview/isolated-kubernetes.md

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

No branches or pull requests

3 participants