Deprecation Policies

[BobWall23]

Just a quick note to emphasize our policies around the containers that we host on our public Google Container Repository (currently Cloaked Search, S3 Proxy, Tenant Security Logdriver, Tenant Security Proxy, and Vendor Bridge).

Containers are tagged with version numbers that follow semver conventions. We do apply security updates to tagged images, which will move the tag to the new image. (We guarantee no changes to functionality, just updates to dependencies to resolve discovered security vulnerabilities.) We strongly encourage you to reference the container images by tag, rather than by image hash. Our deprecation policy guarantees that we will maintain container tags for at least one year after a new version supersedes that tag; for instance, when we release TSP version 4.2.0, a version 4.1.0 TSP container will be available for at least one year. After that time, we will remove the deprecated tag and the container.

When we untag images because we move the tag to a new patched version of the same image, we guarantee that we will retain the old container for six months after it is untagged, in case you are referencing the container by hash. But we only apply security updates to the containers that are tagged, so it is definitely important to move to a new version of the container within that six month period.

Our complete versioning and deprecation policy is available here.