Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[kubernetes-sigs/poseidon] Added chart for firmament-poseidon #4479

Closed
wants to merge 14 commits into from

Conversation

nikita15p
Copy link

@nikita15p nikita15p commented Mar 27, 2018

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 27, 2018
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Mar 27, 2018
@nikita15p nikita15p closed this Mar 27, 2018
@nikita15p nikita15p reopened this Mar 27, 2018
@nikita15p
Copy link
Author

nikita15p commented Mar 27, 2018

/assign @dhilipkumars

@dhilipkumars dhilipkumars changed the title Added chart for firmament-poseidon [WIP] Added chart for firmament-poseidon Mar 27, 2018
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 27, 2018
@dhilipkumars
Copy link
Contributor

dhilipkumars commented Mar 27, 2018

@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.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Apr 2, 2018
@nikita15p
Copy link
Author

Bump to verify CLA.

@unguiculus
Copy link
Member

@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.

@k8s-ci-robot k8s-ci-robot removed the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 16, 2018
@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Apr 16, 2018
@dhilipkumars dhilipkumars changed the title [WIP] Added chart for firmament-poseidon Added chart for firmament-poseidon Jun 18, 2018
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 18, 2018
@dhilipkumars
Copy link
Contributor

dhilipkumars commented Jun 18, 2018

/okay-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 18, 2018
@dhilipkumars dhilipkumars changed the title Added chart for firmament-poseidon [kubernetes-sigs/poseidon] Added chart for firmament-poseidon Jun 18, 2018
@dhilipkumars
Copy link
Contributor

@kubernetes/charts-maintainers PTAL.

Copy link
Member

@unguiculus unguiculus left a 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 -}}
Copy link
Member

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
Copy link
Member

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 }}
Copy link
Member

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 }}
Copy link
Member

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
Copy link
Member

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 }}
Copy link
Member

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}}
Copy link
Member

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 }}
Copy link
Member

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
Copy link
Member

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}}
Copy link
Member

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

@dhilipkumars
Copy link
Contributor

@nikita15p Could you please apply all the review comments on this chart?

@stale
Copy link

stale bot commented Aug 18, 2018

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.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 18, 2018
@mattfarina mattfarina added the Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). label Aug 27, 2018
@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2018
@stale
Copy link

stale bot commented Sep 17, 2018

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.

@stale stale bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 17, 2018
@ey-bot ey-bot removed the Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). label Sep 20, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nikita15p
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: scottrigby

If they are not already assigned, you can assign the PR to them by writing /assign @scottrigby in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This reverts commit 98366b19eadaef49a4bde1e8b5a991c0b02a44fc.
@stale
Copy link

stale bot commented Oct 21, 2018

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.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2018
@stale
Copy link

stale bot commented Nov 4, 2018

This issue is being automatically closed due to inactivity.

@stale stale bot closed this Nov 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants