Skip to content

Conversation

marinoborges
Copy link

@marinoborges marinoborges commented May 27, 2025

Also move DaemonSet manifests to a separate file
&
Make DaemonSet namespace name configurable

Resolve #134


Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.

Changes are automatically published when merged to master. They are not published on branches.

…ests to a separate file & make DaemonSet namespace name configurable

Signed-off-by: Marino Borges <omarinoborges@gmail.com>
@kruise-bot kruise-bot requested review from FillZpp and zmberg May 27, 2025 00:42
@kruise-bot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chrisliu1995 for approval by writing /assign @chrisliu1995 in a comment. For more information see:The Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kruise-bot
Copy link

Welcome @marinoborges! It looks like this is your first PR to openkruise/charts 🎉

Signed-off-by: Marino Borges <omarinoborges@gmail.com>
kind: DaemonSet
metadata:
name: kruise-daemon
namespace: {{ .Values.installation.daemonSet.namespace }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the daemonset installation namespace is not the same as the configuration namespace, plz keep the namespace as is (.Values.installation.namespace)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get what you're saying but it's still unclear to me the purpose of a separate namespace. What is it for?

annotations:
{{ toYaml .Values.serviceAccount.annotations | indent 4 }}
{{- end }}
namespace: {{ .Values.installation.daemonSet.namespace }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the daemonset installation namespace is not the same as the configuration namespace, plz keep the namespace as is (.Values.installation.namespace)

namespace: kruise-system
createNamespace: true
daemonSet:
namespace: kruise-daemon-config
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should rename namespace to config-namespace so as to avoid the confusion between installation namespace

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i agree but this will probably turn it into a major release, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it used to save the pull secrets used by imagepulljobs, so it is not the same as the daemon installation namespace

Signed-off-by: Marino Borges <omarinoborges@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No way to disable kruise-daemon-config namespace from attempting to get created
3 participants