-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[kubernetes-sigs/poseidon] Added chart for firmament-poseidon #4479
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
/assign @dhilipkumars |
@nikita15p Thanks for the PR, there is a lot needs to be done to get this PR in a good shape. Please have a look at best practices. Once all the work is done we could remove [WIP] from the titile. Please sign the Linux Foundation CLA to start with. |
Bump to verify CLA. |
Added maintainer details to Chart.yaml
Added maintainer details to Chart.yaml
@nikita15p You created this as a WIP and did not specify any description. With all due respect but I'm not inclined to review this. We get lots of PRs here which is great and keeps us maintainers busy. But next time, please finish you stuff first and then create a PR. If you have questions on how to implement things, please join Slack and ask there before creating a PR. Thank you. |
/okay-to-test |
@kubernetes/charts-maintainers PTAL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made an initial review. Please read our review guideliones and apply best practices. Apply my comments throughout the chart.
{{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" -}} | ||
{{- end -}} | ||
{{- end -}} | ||
{{- end -}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The two separarte fullname partials may clash. Also, all partials should have the chart name prefix. how about toing this:
{{- define "firmament-poseidon.firmamentFullname" -}}
{{- template "firmament-poseidon.fullname" . -}}-firmament
{{- end -}}
{{- define "firmament-poseidon.poseidonFullname" -}}
{{- template "firmament-poseidon.fullname" . -}}-poseidon
{{- end -}
@@ -0,0 +1,28 @@ | |||
apiVersion: apps/v1beta1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use apps/v1
kind: Deployment | ||
metadata: | ||
name: {{ template "firmament.fullname" .}} | ||
namespace: {{ .Values.namespace }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need the namespace here? It can be passed to the Helm CLI when installing the chart.
template: | ||
metadata: | ||
labels: | ||
scheduler: {{ .Values.firmament.scheduler }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pods should at least have app
and release
labels.
scheduler: {{ .Values.firmament.scheduler }} | ||
spec: | ||
selector: | ||
scheduler: firmament |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you make the label configurable in the deployment, you hard-code it here. Common practice is to use a component
label. Add app
and release
labels.
namespace: {{ .Values.namespace }} | ||
labels: | ||
app: {{ template "firmament-poseidon.name" .}} | ||
chart: {{ .Chart.Name }}-{{ .Chart.Version }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use chart
partial everywhere.
apiVersion: v1 | ||
kind: ServiceAccount | ||
metadata: | ||
name: {{.Values.serviceAccount.name}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You partial from _helpers.tpl
chart: {{ .Chart.Name }}-{{ .Chart.Version }} | ||
heritage: {{ .Release.Service }} | ||
release: {{ .Release.Name }} | ||
name: {{ .Values.clusterrolebinding.name }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resource names should be based on the fullname parial. Is there a reason why you want this to be configurable?
create: true | ||
# The name of the service account to use. | ||
# If not set and create is true, a name is generated using the fullname template | ||
name: poseidon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leave default empty
version: first | ||
poseidonservice: {{ .Values.poseidon.service }} | ||
spec: | ||
serviceAccountName: {{.Values.serviceAccount.name}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use partial for service account
@nikita15p Could you please apply all the review comments on this chart? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nikita15p If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This reverts commit 98366b19eadaef49a4bde1e8b5a991c0b02a44fc.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
What this PR does / why we need it: The firmament-poseidon chart is used to plug in the Poseidon/Firmament scheduler to the Kubernetes cluster.This scheduler augments the current Kubernetes scheduling capabilities by incorporating a new novel flow network graph based scheduling capabilities alongside the default Kubernetes Scheduler.