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

Openmage on K8s. #12

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Openmage on K8s. #12

wants to merge 1 commit into from

Conversation

m-michalis
Copy link

@m-michalis m-michalis commented Oct 7, 2022

My experience on kubernetes is only about 2 months. I've only played locally with minikube. I've wrote this just to get started on this conversation (suggested by @Danieleeffe1) because I did not find any actually useful articles on the web.

This PR just explains how I approached this.

My concerns:

  • database files on, lets say, high availability cloud storage have latency?
  • Media and skin folders? Probably mount ex. s3 bucket via persistentVolume. (with the right setup you can just connect cloudfront to that s3)
  • php-fpm (user: www-data) and nginx (user: nginx) images should run with the same uid and gid while having /media/ and /skin/ shared?
  • any optimizations for db reads and writes regarding having a "true" db for admin and cron and replicas for frontend?
    • I've only worked with small scale (10 orders/minute) projects, so maybe on 1000/sec db should be split/cached (a whole new chapter here)
  • how openmage db upgrade policy should work? (first do the admin pod, then the replicas?)
  • other cache layers?
  • security?

PS: Also this is my very first PR (even as a draft)(in any repository ever) while being a magento developer for over 5 years. 😅

edit: typo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant