You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have successfully deployed osctrl to our k8s cluster. The idea is to deploy the Nginx ingress as the entry point to provide mTLS/TLS termination. After that, the request was forwarded to osctrl-tls.
We also rebuilt the images using KO https://ko.build/ to minimize the vulnerability.
We currently using pure manifest with kustomization and would like to share these manifests if accepted.
The text was updated successfully, but these errors were encountered:
@javuto Do you have a plan to host the docker image for osctrl. We can simply use the github container registry.
As I mentioned, we use the ko to build the production-ready multi-platform distroless images, which only contain the minimum package for running the application.
Here is the example image for osctrl-tls. You can see that the image size is around 20MB without any vulnerability.
However, for osctrl-admin, it needs some adjustment due to static assets. I am also happy to provide production level dockerfile if you believe dockerfile is a better choice.
We have successfully deployed osctrl to our k8s cluster. The idea is to deploy the Nginx ingress as the entry point to provide mTLS/TLS termination. After that, the request was forwarded to osctrl-tls.
We also rebuilt the images using KO https://ko.build/ to minimize the vulnerability.
We currently using pure manifest with kustomization and would like to share these manifests if accepted.
The text was updated successfully, but these errors were encountered: