mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #1175] Possible to deploy using Docker / K8s? #639
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#639
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joeldeteves on GitHub (Oct 30, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1175
We are a heavy Kubernetes user - all of our internal apps are dockerized and run in a k8s cluster.
I'm wondering, is it possible the way this app is written now to dockerize it?
IE, are there specific reasons that require it to run as an Azure Static Web App?
@KelvinTegelaar commented on GitHub (Oct 30, 2022):
No, cipp is writen specificly for swa and azure functions, you cannot use it in a container.
@joeldeteves commented on GitHub (Oct 30, 2022):
Answered my own question - TLDR; even though it's not supported (and I don't expect you to support it), it is possible to run Azure functions in a local docker container https://hub.docker.com/_/microsoft-azure-functions-node
@KelvinTegelaar commented on GitHub (Oct 30, 2022):
Even then it wont work, you will still need something to handle authentication, which is currently done by swa. To even be able to access the frontend you will need to completely recode how the frontend handles claims, Then there's credential management which requires kv, and then you'll need to make the api endpoint available via the same endpoint somehow. Even if you hack it all together it's going to be a terrible experience.