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

Add portus chart #2766

Closed
wants to merge 31 commits into from
Closed

Add portus chart #2766

wants to merge 31 commits into from

Conversation

rendhalver
Copy link
Collaborator

This is a resubmit of #1284.
Thanks to @so0k for all the hard work!
This is currently the same as the last commit in that PR.

It looks like there are a few differences in layout since that PR was submitted so I will try to address those concerns as I go.
There were also a few concerns not address in the original PR so I will address those as well.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 16, 2017
@unguiculus
Copy link
Member

Please check our best practices, especially those on naming resources and standard labels. Resource metadata should generally look like so:

name: {{ template "portus.fullname" . }}
labels:
  heritage: {{ .Release.Service }}
  release: {{ .Release.Name }}
  chart: {{ .Chart.Name }}-{{ .Chart.Version }}
  app: {{ template "portus.name" . }}

@rendhalver
Copy link
Collaborator Author

Thanks @unguiculus I will get those fixed.

@rendhalver
Copy link
Collaborator Author

@unguiculus This Chart has multiple components but there isn't a definition $component.name in the _helpers.tpl file and I am not sure of the proper way to do that.
Can you point me to some docs on how to achieve that?

On a side note I am very tempted to split out the registry component into it's own chart and then add that as a requirement for this chart so the templates are a bit simpler.

I am also new to writing Charts so I am still learning how best to do them.

@unguiculus
Copy link
Member

There's a chart for Docker registry already: https://github.com/kubernetes/charts/tree/master/incubator/docker-registry

@rendhalver
Copy link
Collaborator Author

True. I forgot about that Chart.
I had already discounted that because doesn't have the options we need to setup the registry for Portus.
Maybe I can expand that one so it can be configured with those extra options.

As for my other question what is the best way to define those $component.name variables?

@rendhalver
Copy link
Collaborator Author

@unguiculus I think worked out what I needed to change.
The latest commit addresses the label inconsistencies.

@unguiculus
Copy link
Member

Please create a PR for the registry chart to add the stuff you need. We should also see that we can move it to stable so you can use it.

@rendhalver
Copy link
Collaborator Author

Will do.
Thanks for the help @unguiculus It is much appreciated. :)

@so0k
Copy link
Contributor

so0k commented Nov 20, 2017

The reason I had them bundled was the auth token service configuration required on the registry side.

If the registry chart exposes that, it should be fine to define it as a dependency though

@rendhalver
Copy link
Collaborator Author

@unguiculus What else needs changing in the docker-registry chart to move it to stable?

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 24, 2017
@viglesiasce
Copy link
Contributor

/ok-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 Nov 27, 2017
@rendhalver
Copy link
Collaborator Author

@viglesiasce This is dependent on my other PR for getting docker-registry usable and put of incubator #2801. Once that is sorted I can update this to reflect the new location of docker-registry.

@unguiculus
Copy link
Member

unguiculus commented Nov 29, 2017

I think the Docker registry chart looks pretty good. I'd suggest you create a PR to move it to stable.

apiVersion: v1
name: portus
home: http://port.us.org/
version: 0.1.0
Copy link
Member

Choose a reason for hiding this comment

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

Add appVersion

- https://github.com/docker/distribution/
- https://github.com/Nordstrom/kube-registry
maintainers:
- name: Vincent De Smet
Copy link
Member

Choose a reason for hiding this comment

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

Use Github username

Copy link
Contributor

Choose a reason for hiding this comment

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

can remove me if this is holding back the merge :)

@rendhalver
Copy link
Collaborator Author

It needs to be redone or rebased. Redoing it seems quicker at this stage. #2612 got merged that changed a lot of the docker-registry chart.
I will get that sorted when I get a chance.

@rendhalver
Copy link
Collaborator Author

The docker-registry PR has been redone in #2926.

@rendhalver
Copy link
Collaborator Author

@unguiculus This is my PR to promote docker-registry to stable: #2944
I can update the requirements on this once that is merged.

@rendhalver
Copy link
Collaborator Author

/retest

@unguiculus
Copy link
Member

Let's try it again. Timeouts have been increased.

@k8s-ci-robot k8s-ci-robot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 14, 2018
@rendhalver
Copy link
Collaborator Author

Thanks I will get that fixed.

@rendhalver
Copy link
Collaborator Author

Why didn't that failure fail the build?

@davidkarlsen
Copy link
Member

@rendhalver Have a look at helm/chart-testing#9

@unguiculus
Copy link
Member

/retest

@unguiculus
Copy link
Member

/test pull-charts-e2e

@rendhalver
Copy link
Collaborator Author

I see what's going on.
It's the problem we had with testing before where the deploy is assuming the Secret exists before the chart it setup.
I will put in the code to create those certs if they don't exist.

metadata:
name: "{{ .Release.Name }}"
labels:
app: {{ template "portus.name" . }}
Copy link
Member

Choose a reason for hiding this comment

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

Add release label to selector.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks for the reminder.
I will get that fixed.

name: "{{ .Release.Name }}"
labels:
app: "{{ template "portus.name" . }}"
component: minio
Copy link
Member

Choose a reason for hiding this comment

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

Add release label to selector.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks for the reminder.
I will get that fixed.

Pete Brown and others added 3 commits August 15, 2018 11:08
Previosly we assumed the cert for the secrets existed.
This moves the creation of that secret into the chart.
If no certs are provided we generate them
@k8s-ci-robot
Copy link
Contributor

@rendhalver: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
pull-charts-e2e f7999bb link /test pull-charts-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@unguiculus
Copy link
Member

With the latest chart-testing fix the CI job finally fails as expected.

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

stale bot commented Sep 15, 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 Sep 15, 2018
# Various IDEs
.project
.idea/
*.tmproj
Copy link
Collaborator

@giacomoguiulfo giacomoguiulfo Sep 15, 2018

Choose a reason for hiding this comment

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

Please add the OWNERS file in the .helmignore - https://github.com/helm/charts#owning-and-maintaining-a-chart

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

stale bot commented Oct 15, 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 15, 2018
@stale
Copy link

stale bot commented Oct 29, 2018

This issue is being automatically closed due to inactivity.

@stale stale bot closed this Oct 29, 2018
@flavio
Copy link
Contributor

flavio commented Oct 30, 2018

Triggering the reopening of this issue. @mssola is going to take care of that unless @rendhalver or others have something against it.

@rendhalver
Copy link
Collaborator Author

I am happy to help get it working. I haven't had the time to devote to it lately.
I am also happy to be a maintainer and OWNER if you need one.

@rendhalver
Copy link
Collaborator Author

And thanks. :)
I had a few ideas on how to get it working but didn't get time top test them.
Ping my on your new PR and I will add those thoughts there.

@bklang bklang deleted the feature/portus branch December 30, 2018 20:14
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. Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

10 participants