feat: add controller rock (v0.11.2)

[NohaIhab]

closes #32

[DnPlas]

Thanks @NohaIhab ! For some reason I am not able to build the rock to test it. Do you think there is something wrong with my setup? I get this:

ubuntu@charm-dev-jammy:~/kserve-rocks/controller$ rockcraft --version
rockcraft 1.2.2
ubuntu@charm-dev-jammy:~/kserve-rocks/controller$ rockcraft pack
ubuntu@charm-dev-jammy:~/kserve-rocks/controller$ ls
rockcraft.yaml  tests  tox.ini
ubuntu@charm-dev-jammy:~/kserve-rocks/controller$

[NohaIhab]

@DnPlas that's odd, is there no output from the pack command? maybe try rockcraft pack -v for logs?

[NohaIhab]

@DnPlas you can download the rock from the CI's artifacts in the meantime

[DnPlas]

Thanks @NohaIhab I was able to build the image, it was an issue on my environment (I am using an arm machine).

On another topic, I saw at the beginning you defined an entrypoint, but that caused an issue, do you know why it was the case for you and not for other rocks? For instance, this one.

[NohaIhab]

On another topic, I saw at the beginning you defined an entrypoint, but that caused an issue, do you know why it was the case for you and not for other rocks? For instance, this one.

@DnPlas
defining an entrypoint did not cause an issue, it's just unnecessary when we are not expecting additional arguments to be passed to the container when it's being started. See the rockcraft docs.

[DnPlas]

Thanks @NohaIhab !

[orfeas-k]

Thank you @NohaIhab :)