Skip to content

Pack file hash code is different on different Kubernetes pods #16

Description

@ol-vrobison

When deployed to a Kubernetes cluster, the name of combined.xxxxx.pack changes based on the pod it's running on. This means that if I have multiple pods for the same service and don't have sticky sessions enabled, I get 404 messages when trying to load a file that does not exist on one of the pods. E.g. pod 1 has combined.js.h840864473.pack, a refresh of the page can take me to a different pod to fetch the pack file, which returns 404, because the second pod was expecting a different pack file, e.g. combined.js.h-238451380.pack.

I understand that this project is not being maintained, but could you provide insight into why this happens? Is there a pseudo random element to how the hash for the file name is created? Is there a way to override it?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions