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

Add Varnish #309

Merged
merged 39 commits into from
Jun 18, 2020
Merged

Add Varnish #309

merged 39 commits into from
Jun 18, 2020

Conversation

kierenevans
Copy link
Contributor

@kierenevans kierenevans commented Jun 1, 2020

If varnish is in the list of services:

  • Use varnish as the entrypoint from traefik.
  • Use tls-offload as the target for acceptance testing (behat) within the docker-compose environment to provide TLS support.
  • Deploy varnish statefulset to pipeline environments as the entrypoint from the ingress.
  • Deploy a configmap containing the varnish configuration, to avoid wiping out the cache on each deployment if built with docker image+configuration per-commit.
  • Configure the "timeout chain" of varnish and nginx to be the max execution time of php plus one or two seconds. The idea is to never show a 502/504 when php is still working, though this may not be true if PHP is performing slow network requests as they block and don't count towards max_execution_time, or if the queue to access php-fpm from nginx is high.
  • BREAKING CHANGE: .Values.ingress renamed to .Values.ingress.type to allow for more ingress configurations.
  • Magento 2 VCL from https://github.com/magento/magento2/blob/2.3.5/app/code/Magento/PageCache/etc/varnish6.vcl used as the configuration.
  • Magento 2 env.php configured for http_cache_hosts

Fixes #14

@kierenevans kierenevans added enhancement New feature or request wip Good for newcomers harness-all Changes required to all harness directories breaking Breaking change, next major release only labels Jun 1, 2020
@kierenevans kierenevans force-pushed the feature/add-varnish-entrypoint branch from b5efe80 to 094bd01 Compare June 2, 2020 09:31
@kierenevans kierenevans marked this pull request as ready for review June 2, 2020 10:47
@kierenevans kierenevans added wip Good for newcomers and removed wip Good for newcomers labels Jun 2, 2020
@kierenevans kierenevans force-pushed the feature/add-varnish-entrypoint branch from d3981ce to 48e2243 Compare June 2, 2020 10:52
@kierenevans kierenevans removed the wip Good for newcomers label Jun 2, 2020
tkotosz
tkotosz previously approved these changes Jun 5, 2020
Copy link

@tkotosz tkotosz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

generally looks good to me. @dcole-inviqa could you please have a look at this, just to be on the safe side since it is a breaking change?

@tkotosz tkotosz requested a review from coledave June 5, 2020 07:40
@kierenevans kierenevans added this to the 0.8.0 milestone Jun 9, 2020
@kierenevans kierenevans force-pushed the feature/add-varnish-entrypoint branch 2 times, most recently from 43aa908 to 5935b6a Compare June 18, 2020 07:11
@kierenevans kierenevans force-pushed the feature/add-varnish-entrypoint branch from 5935b6a to 63bb716 Compare June 18, 2020 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking change, next major release only enhancement New feature or request harness-all Changes required to all harness directories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add option for varnish container as the entrypoint to the site in Magento 2.x harness
3 participants