myros

One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are <a href="https://www.varnish-cache.org/" rel="nofollow ugc">Varnish</a> and <a href="https://www.nginx.com/" rel="nofollow ugc">Nginx</a>. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’s disk space.
The Remote Cache Purger plugin sends a request to delete (aka flush) the cached data of a page or post to remote server(s).
<h4>How It Works</h4>
Manually

Remote Cache Purger

Plugin will empty remote server's cache content (only NGINX at this moment). Plugin Features Purge cache on multiple NGINX servers Cache can b …

Calin Don

The plugin surfaces information from the underlying cluster to your WordPress site. It’s aim is to better understand what’s happening with your site while it runs on a Kubernetes cluster.
<h3>Current and upcoming features</h3>
<ul>
<li>Kubernetes info – displays the Kubernetes control plane version right into the site health-check</li>
<li>Pod information – displays the pod runtime information</li>
<li>ToDo: Multisite ingress – manage Kubernetes ingress resources for multi site deployments</li>
<li>ToDo: Deployment health – run health checks for the deployment the current pod is part of</li>
<li>ToDo: Manage deployment scaling – allows to scale the deployment up and down right from your WordPress dashboard</li>
<li>ToDo: List all deployment’s pods – list all pods from managed by the deployment and surfaces info regarding them.</li>
</ul>

Remote Cache Purger vs Bitpoke Kubernetes