Skip to content

Latest commit

 

History

History
208 lines (120 loc) · 9.28 KB

File metadata and controls

208 lines (120 loc) · 9.28 KB

Upgrade notes

How to Upgrade

  1. In composer.json upgrade shopsys/deployment to new version:
    - "shopsys/deployment": "~2.1.3",
    + "shopsys/deployment": "~3.0.0",
  2. Run composer update shopsys/deployment
  3. Check files in mentioned pull requests and if you have any of them extended in your project, apply changes manually

Upgrade from v4.6.1 to v5.0.0

  • remove files that are already part of project-base by default (#66)
  • if your project does not include nginx.yaml file for Kubernetes deployment, you need to copy-paste the file from project-base repository into app/orchestration/kubernetes/configmap/nginx.yaml in your project

Upgrade from v4.6.0 to v4.6.1

  • fix redirects within imageResizer (#68)

Upgrade from v4.5.0 to v4.6.0

  • upgraded nginx to version 1.29 (#67)

Upgrade from v4.4.0 to v4.5.0

  • added gopay payment notification url handled by backend with fallback to storefront (#65)

Upgrade from v4.3.0 to v4.4.0

  • yq was updated to the newest version (#63)
    • If you are using shopsys/kubernetes-buildpack:1.x in your GitLab CI pipeline, update it to shopsys/kubernetes-buildpack:2.0

Upgrade from v4.1.1 to v4.2.0

  • improved nginx configuration (#59)

Upgrade from v4.1.0 to v4.1.1

  • fix 403 error for cloudflare ingress in production (#60)
  • rabbitmq is now running on normal nodes (#58)

Upgrade from v4.0.11 to v4.1.0

  • enabled setting domain with postfix in URL (#57)

Upgrade from v4.0.10 to v4.0.11

  • Respect IP whitelisting and HTTP auth for not production environment (#56)

Upgrade from v4.0.9 to v4.0.10

  • Upgrade RabbitMQ (#55)

Upgrade from v4.0.8 to v4.0.9

  • Update allowed IP address pools in nginx.yaml for location ~ ^/resolve-friendly-url if you are using custom IP address pools in your cluster
  • Added Cloudflare support (#54)

Upgrade from v4.0.7 to v4.0.8

  • Remove CPU request limits (#53)

Upgrade from v4.0.6 to v4.0.7

  • Horizontal autoscaler for PHP-FPM now checks only PHP-FPM container (#49)
  • Update resource requests and limits by best practices (#50)
  • Add tolerations to Cron, RabbitMQ and Consumers to be able to run only on selected nodes (#51)

Upgrade from v4.0.5 to v4.0.6

  • prepare prometheus exporters for Redis and RabbitMQ (#48)

Upgrade from v4.0.4 to v4.0.5

  • optimize cpu and memory resources (#47)

Upgrade from v4.0.3 to v4.0.4

  • Follow redirects when checking if domains is running (#46)

Upgrade from v4.0.2 to v4.0.3

  • Minor improvements (#45)
    • Containers are pulled only if are not already downloaded
    • You can now define your custom rabbitmq URL by RABBITMQ_DOMAIN_HOSTNAME variable
    • Storefront autoscaling is now managed separately by MIN_STOREFRONT_REPLICAS and MAX_STOREFRONT_REPLICAS variables

Upgrade from v4.0.1 to v4.0.2

  • Optimize Redis configuration (#44)

Upgrade from v4.0.0 to v4.0.1

  • Do not log notice messages after PHP-FPM starts (#42)
  • Refactor consumers logging and restarting (#43)

Upgrade from v3.3.4 to v4.0.0

  • Upgrade manifests for newer versions of kubernetes (#39)
  • upgrade rabbitmq ingress manifest (#40)
  • enable logging for consumers (#41)

Upgrade from v3.3.3 to v3.3.4

  • Check all domains at the end of deploy process (#37)

Upgrade from v3.3.2 to v3.3.3

  • Fix problems with deployment (#35)

Upgrade from v3.3.1 to v3.3.2

  • Redis was upgraded to version 7.4-alpine (#34)
    • If you are using older Redis version then define REDIS_VERSION='redis:7.0-alpine' with using version in your deploy-project.sh file

Upgrade from v3.3.0 to v3.3.1

  • Finding running container for after deploy tasks is fixed (#33)

Upgrade from v3.2.9 to v3.3.0

  • Cron can run under Alpine Linux (#31)

Upgrade from v3.2.7 to v3.2.9

  • Added routes to Nginx (Commit)
  • RunAsUser was removed from Kubernetes manifests (#30)

Upgrade from v3.2.6 to v3.2.7

  • upgraded PHP-FPM and Nginx configuration (#29)
    • If you are using shopsys/kubernetes-buildpack:1.1 in your Gitlab CI pipeline, update it to shopsys/kubernetes-buildpack:1.2
    • This upgrade will work only with kubectl client in version 1.25+ (Upgraded in shopsys/kubernetes-buildpack:1.2)

Upgrade from v3.2.5 to v3.2.6

  • blocked dynamic content on CDN now returns 403 code (#27)

Upgrade from v3.2.4 to v3.2.5

  • returns only static content from vshosting CDN (#25)

Upgrade from v3.2.3 to v3.2.4

  • nginx app location for customer uploaded file added (#21)

Upgrade from v3.2.2 to v3.2.3

  • implemented script to send slack notification about deployment process (#23)
  • updated fpm workers and set terminate timeout (#24)

Upgrade from v3.2.1 to v3.2.2

  • upgraded nginx to version 1.27.0 (#21)

Upgrade from v3.2.0 to v3.2.1

  • consumer manifests are created properly for the first deploy (#20)

Upgrade from v3.1.0 to v3.2.0

  • upgraded PHP-FPM and Nginx configuration (#19)

Upgrade from v3.0.4 to v3.1.0

  • added social-network url for redirecting to backend (#17)

Upgrade from v3.0.3 to v3.0.4

  • Warmup Symfony cache after start php container (#18)

Upgrade from v3.0.0 to v3.0.1

  • fix incorrect order of redirect requests (#15)

Upgrade from v2.1.3 to v3.0.0

  • refactor working with whitelisted IP addresses (#11)
  • fix redirect chain (#12)
  • correctly call self domain from container (#13)
  • improve configuration for Redis (#14)

Upgrade from v2.1.2 to v2.1.3

  • added security headers for more safety (#10)

Upgrade from v2.1.1 to v2.1.2

  • update your deploy-project.sh to properly deploy consumer manifests (#9)

Upgrade from v2.1.0 to v2.1.1

Upgrade from v2.0.1 to v2.1.0

  • clear Redis cache only once instead of at every container start (#7)
    • phing target clean-redis-storefront is available from shopsys/framework v14.0.0

Upgrade from v1.1.0 to v2.0.1

  • use image proxy for images (#5 and #6)
    • the @imageResizer PHP script is available from shopsys/project-base v14.0.0
    • be sure to verify the images redirection regex matches your application settings
      • all the image sizes are explicitly included in the regex so if your application uses another sizes, you need to update the regex to match your application settings
      • you might need to create your own storefront nginx config file for that purpose