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

Feature proposal for v1.1.0-rc #4

Open
liangrog opened this issue Aug 2, 2020 · 0 comments
Open

Feature proposal for v1.1.0-rc #4

liangrog opened this issue Aug 2, 2020 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@liangrog
Copy link
Owner

liangrog commented Aug 2, 2020

Here are the list of features/fixes are proposed for v1.1.0-rc:

DaemonSet:

  • Distinguish daemonset pod so when daemonset get deployed to the designated namespace, only the nodes pinned to the namespace are being scheduled. The same daemonset's pods won't be schedule in other nodes causing 'pending' issue.
  • Exclusion daemonset option so even daemonset can be deployed to the designated namespace but not pinned to the nodes.

Namespace configuration

  • Provide option for default nodes regardless what namespace pods are deployed to. In addition, provide blacklist namespaces which will be disregarded. By Default, system namespaces such as kube-system are disregarded in this setting.
  • Provide Namespace/node label configuration by adding annotation to namespace resource.
  • Provide guarding only option, which will only check if nodeselector is defined with correct labelling, but not to change if misconfiguration found. It'll ailed the deployment so to enforce user to make sure nodeselector is inlined.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant