Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from AKS to container apps #13079

Open
Tracked by #11574
mirkoSekulic opened this issue Jul 3, 2024 · 0 comments
Open
Tracked by #11574

Migrate from AKS to container apps #13079

mirkoSekulic opened this issue Jul 3, 2024 · 0 comments
Labels
status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design.

Comments

@mirkoSekulic
Copy link
Collaborator

mirkoSekulic commented Jul 3, 2024

Why

Maintaining an AKS can be time-consuming and as we don't have too many resources in the team, ideally we would like to use outsourced infrastructure. In addition to that we only have few simple services hosted in our cluster.

What

Move away from AKS to container apps

Blockers

One of the main reasons why we have AKS in the place is mostly due to mounted premium disks in our self-hosted Gitea. Gitea didn't support azure blob storage as a storage type.
Since Gitea will support blob storage from version 1.23, ref: go-gitea/gitea#30995,
Then it will be possible to move from mounted disks.

Designer service is using non-premium mounted disks as well but that is not a big deal since that can be done in container apps as well.

Notes

We have a pretty good deployment mechanism with Flux, but we’ll lose that if we move to container apps.

Steps

Move Gitea storage to Azure Blob storage
Move services to container apps.

@mirkoSekulic mirkoSekulic converted this from a draft issue Jul 3, 2024
@mirkoSekulic mirkoSekulic added the status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design.
Projects
Status: No status
Development

No branches or pull requests

1 participant