-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Conversation
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" . }} |
Thanks @unguiculus I will get those fixed. |
@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. 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. |
There's a chart for Docker registry already: https://github.com/kubernetes/charts/tree/master/incubator/docker-registry |
True. I forgot about that Chart. As for my other question what is the best way to define those $component.name variables? |
@unguiculus I think worked out what I needed to change. |
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. |
Will do. |
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 |
@unguiculus What else needs changing in the docker-registry chart to move it to stable? |
/ok-to-test |
@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. |
I think the Docker registry chart looks pretty good. I'd suggest you create a PR to move it to stable. |
stable/portus/Chart.yaml
Outdated
apiVersion: v1 | ||
name: portus | ||
home: http://port.us.org/ | ||
version: 0.1.0 |
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.
Add appVersion
stable/portus/Chart.yaml
Outdated
- https://github.com/docker/distribution/ | ||
- https://github.com/Nordstrom/kube-registry | ||
maintainers: | ||
- name: Vincent De Smet |
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 Github username
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.
can remove me if this is holding back the merge :)
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. |
The docker-registry PR has been redone in #2926. |
@unguiculus This is my PR to promote docker-registry to stable: #2944 |
106bc89
to
0a637c4
Compare
/retest |
Let's try it again. Timeouts have been increased. |
Thanks I will get that fixed. |
Why didn't that failure fail the build? |
@rendhalver Have a look at helm/chart-testing#9 |
/retest |
/test pull-charts-e2e |
I see what's going on. |
metadata: | ||
name: "{{ .Release.Name }}" | ||
labels: | ||
app: {{ template "portus.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.
Add release
label to selector.
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.
Thanks for the reminder.
I will get that fixed.
name: "{{ .Release.Name }}" | ||
labels: | ||
app: "{{ template "portus.name" . }}" | ||
component: minio |
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.
Add release
label to selector.
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.
Thanks for the reminder.
I will get that fixed.
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
@rendhalver: The following test failed, say
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. |
With the latest chart-testing fix the CI job finally fails as expected. |
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. |
# Various IDEs | ||
.project | ||
.idea/ | ||
*.tmproj |
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.
Please add the OWNERS file in the .helmignore - https://github.com/helm/charts#owning-and-maintaining-a-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 is being automatically closed due to inactivity. |
Triggering the reopening of this issue. @mssola is going to take care of that unless @rendhalver or others have something against it. |
I am happy to help get it working. I haven't had the time to devote to it lately. |
And thanks. :) |
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.