Replies: 2 comments 2 replies
-
|
Not currently possible, but only because no one has asked for this. Ideally, what is the workflow you'd want here? Just the same |
Beta Was this translation helpful? Give feedback.
-
|
Ideally, it would be great if I didn't have to touch k3s at all for this. Ideally, I would like to configure everything solely with dokku commands. dokku However, |
Beta Was this translation helpful? Give feedback.
-
|
Mind filing a ticket for this? We can probably easily do the |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for coming back with this so late. Created a feature request #7204 Thank you |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am currently trying to migrate from the old dokku-scheduler-kubernetes scheduler to the new k3s scheduler.
In one of my apps, I have a process that needs to be accessible on TCP port 13000. With the old scheduler, I used the service-process-types so that the process gets exposed on port 5000, and then used a
ConfigMapto expose it withingress-nginx.Is it somehow possible to do this with the new k3s scheduler? How can I tell Dokku to expose another process, besides the web process, to get an open port?
Beta Was this translation helpful? Give feedback.
All reactions