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
The controller can serve the console on the mgmt API's web listener as a new binding "zac." Presently, it's necessary for the user to separately download and mount a directory containing the console's SPA build.
The simplest experience and simplest solution to implement is to build the SPA in to the controller image, but the console would add ~70MiB to an already huge ~500MiB.
At a minimum, provide a Dockerfile for the controller that sources a release image and adds the console.
Ideally, we'd vend some image that has the console and controller, whether that's a console container that pins a controller version, or vice versa.
The text was updated successfully, but these errors were encountered:
For this first round, I'll ship the console SPA (70MiB) as part of the main controller image. Let me know if the increase in size is a barrier to adoption for you.
The controller can serve the console on the mgmt API's web listener as a new binding "zac." Presently, it's necessary for the user to separately download and mount a directory containing the console's SPA build.
The simplest experience and simplest solution to implement is to build the SPA in to the controller image, but the console would add ~70MiB to an already huge ~500MiB.
At a minimum, provide a Dockerfile for the controller that sources a release image and adds the console.
Ideally, we'd vend some image that has the console and controller, whether that's a console container that pins a controller version, or vice versa.
The text was updated successfully, but these errors were encountered: