[GH-ISSUE #1175] Possible to deploy using Docker / K8s? #639

Closed
opened 2026-03-02 12:43:55 +03:00 by kerem · 3 comments
Owner

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?

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?
kerem closed this issue 2026-03-02 12:43:55 +03:00
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 30, 2022):

No, cipp is writen specificly for swa and azure functions, you cannot use it in a container.

<!-- gh-comment-id:1296167969 --> @KelvinTegelaar commented on GitHub (Oct 30, 2022): No, cipp is writen specificly for swa and azure functions, you cannot use it in a container.
Author
Owner

@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

<!-- gh-comment-id:1296313489 --> @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
Author
Owner

@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.

<!-- gh-comment-id:1296314224 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#639
No description provided.