The hardened image protects the release path while blocking services from becoming ready.
Startup reliability depends on a correction that keeps the image's security baseline intact.
Who you’d be doing this for
“My admins saw search go unavailable again after the release, and they want to know whether access is affected.”
Tyra Lund · IT Platform Owner
Responsible for dependable access to the enterprise knowledge index across connected business systems.
What is at stake
Permission-hierarchy services are failing readiness checks after deployments built from a hardened image. You have to weigh a fast image correction against retaining the security controls that cleared the release.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- release readiness vs. hardened-image integrity
- fast correction vs. repeatable evidence
- storage compatibility vs. shared image consistency
Why Glean
Permission-aware retrieval depends on services that can load and enforce permission hierarchies reliably.
Written with these in mind
Not your kind of problem? 29 more at Glean, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.