Conversation
|
Review required by @laverman as hawkBit representative in the Packages project |
|
The problems seems to be usage of rabbitmq chart from bitnami repo, which is not added in ct.yaml |
laverman
left a comment
There was a problem hiding this comment.
Great to see this contribution here! 👍
Just some general comments:
- Would you mind adding a license header to the
*.yamlfiles? - I triggered the CI-actions again, to see if #17 fixed the failed check.
- I don't want to start a big naming discussion, whether to name it "eclipse-hawkbit" or "hawkbit-update-server" ;-) However, in order to be consistent with ditto, it might make sense to go with the former (knowing that hawkBit named its docker image "hawkbit-update-server") ... What do you think?
- Also in accordance with ditto, shall we add a Local Setup section to the readme as well? (Could also be part of another PR)
Please find my other comments in the respective files.
| env: | ||
| - name: SPRING_PROFILES_ACTIVE | ||
| value: "{{ .Values.spring.profiles }}" | ||
| - name: MANAGEMENT_SERVER_PORT |
There was a problem hiding this comment.
What is this property used for?
If you want to change hawkBit's server port SERVER_PORT would be the correct property.
There was a problem hiding this comment.
It configures the SpringBoot management server port. The port is used for the probes.
(ref: https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-features.html#production-ready-customizing-management-server-port)
If you agree I'll keep this confiugration.
There was a problem hiding this comment.
Understood. However, as there are no actual actuator endpoints (e.g. health, metrics, ...) available, I was wondering whether to just use the hawkBit landing page for the probes?
| - name: http | ||
| containerPort: 8080 | ||
| protocol: TCP | ||
| - name: management |
| ## Configuration for the device management federation | ||
| ## ref: https://www.eclipse.org/hawkbit/apis/dmf_api/ | ||
| dmf: | ||
| hono: |
There was a problem hiding this comment.
The following configuration requires eclipse-hawkbit/hawkbit#890 to be merged. I'm not sure, if we should include it right away, since 0.3.0-M5 doesn't support it?
There was a problem hiding this comment.
I'm way unsure, but might you mean this PR eclipse-hawkbit/hawkbit#865?
There was a problem hiding this comment.
The properties in this section are not supported by hawkBit as of now. They will be introduced with eclipse-hawkbit/hawkbit#890 as they configure Hono to be used as device registry for hawkBit via DMF. As these properties will have no effect at the moment, I was wondering whether to exclude them for now.
There was a problem hiding this comment.
I commented the properties and added a reference to the related PR.
Is this okay for you?
ff8d458 to
3790337
Compare
|
Please don't merge. I want to try to fix the ci. Currently pvc were disabled. |
|
CI works now with persistence by using a forked kind action https://github.com/eclipse/packages/pull/18/files#diff-60fe268f71ae7f8409aff40d0a3e51d8R61 I've create a pr at the helm folks kind action repo to get it merged: helm/kind-action#16 Not sure if we want to go with my temporary version or wait for their merge. |
|
Let's wait a day or two and see how it goes. |
|
On another topic: When using the original helm charts for hawkbit from kiwigrid, I had to make some changes to be able to run with non-root containers. Is root still a requirement, or can we maybe get rid of that requirement from the start? I made a few modifications in order to drop the requirement, but I don't want to mess up your efforts 😉 |
|
+1 for non root As we're waiting anyway, we could maybe add the changes here? Do you have a link to your changes? |
|
Not to the changes, but to the content: https://github.com/ctron/hawkbit-kubernetes |
|
@axdotl @monotek This PR now seems to contain arbitrary changes to all kinds of artifacts, e.g. the general IoT Packages README, the CI pipeline and, last but not least, the hawkBit chart itself which originally seemed to be the subject of this PR :-) |
|
Sure, no problem. I will create separate pr for the ci stuff. |
|
i've created the pr: #23 |
|
@sophokles73 With respect to the Next to that I followed @sophokles73 advice and reverted the CI related changes. What do you think - can we proceed and get this PR merged once @laverman re-reviewed it? |
monotek
left a comment
There was a problem hiding this comment.
I still think persistence should be enabled by default.
Using empty dir is potentially dangerous and should only be used if you activly enable it.
|
Could you re-base the PR? |
|
I added a small PR for this PR -> kiwigrid#1 … This drops the default requirement to run as user 1001, and lets the cluster assign a random user uid, which makes it work on OpenShift. You can of course always re-enable the uid 1001 requirement. |
|
I've added the needed stuff to run the container as non root user now. But as already mentioned in the comment to your pr (kiwigrid#1 (review)) i don't like to disable this by default. |
Signed-off-by: André Bauer <andre.bauer@kiwigrid.com>
ctron
left a comment
There was a problem hiding this comment.
I still think the PR needs a rebase, but 👍 in any case.
done. |
|
Yay! Thanks for all the work! |
Signed-off-by: Axel Köhler axel.koehler@kiwigrid.com
This PR will add the Hawkbit update server chart to the packages project.
Feedback is highly appreciated.