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

generate-yaml volcano-monitoring-latest.yaml diffrent #3779

Open
lengrongfu opened this issue Oct 17, 2024 · 6 comments · May be fixed by #3781
Open

generate-yaml volcano-monitoring-latest.yaml diffrent #3779

lengrongfu opened this issue Oct 17, 2024 · 6 comments · May be fixed by #3781
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@lengrongfu
Copy link
Contributor

Description

When i change chart file, then exec make generate-yaml TAG=latest RELEASE_DIR=installer command, every time volcano-monitoring-latest.yaml this file will change, remove the following code.

nodeSelector:
node.kubernetes.io/instance-type: controlpanel

because $kube_state_metrics_ns this var is not value.

{{ if $kube_state_metrics_ns }}
nodeSelector: {{- toYaml $kube_state_metrics_ns | nindent 8 }}
{{ end }}

{{ $kube_state_metrics_ns := or .Values.custom.kube_state_metrics_ns .Values.custom.default_ns }}

I found in values.yaml file not define value for this two var .Values.custom.kube_state_metrics_ns and .Values.custom.default_ns.

I can't trace the history.

Can someone tell me how I should modify it? is change volcano-monitoring-latest.yaml this file or and node select to values.yaml?

Steps to reproduce the issue

Describe the results you received and expected

Hope exec make generate-yaml TAG=latest RELEASE_DIR=installer this command, no other changes will occur.

What version of Volcano are you using?

master

Any other relevant information

No response

@lengrongfu lengrongfu added the kind/bug Categorizes issue or PR as related to a bug. label Oct 17, 2024
@lengrongfu
Copy link
Contributor Author

/good-first-issue

@volcano-sh-bot
Copy link
Contributor

@lengrongfu:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@volcano-sh-bot volcano-sh-bot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Oct 17, 2024
@lengrongfu
Copy link
Contributor Author

/assign

@fengruotj
Copy link
Contributor

fengruotj commented Oct 17, 2024

@volcano-sh-bot I am very interested in this issue, please assign it to me. Maybe, we can remove the nodeSelector default value from the volcano/installer/volcano-monitoring-latest.yaml file.

@Monokaix
Copy link
Member

caused by #3740

@fengruotj
Copy link
Contributor

@lengrongfu @Monokaix Hi all, maybe we can remove the default nodeSelector value from the volcano monitoring installation yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
4 participants