Running Infisical?

Infisical operator stuck or overrides invisible? We unstick it.

Infisical covers much of the same territory as Doppler with an open-source core, but the Kubernetes operator, the override semantics and the self-hosted path each have their own sharp edges. We settle the operator, trace the auth flow and sort the override visibility until every pod reads the secret the policy actually intended.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

infisical-operator.log

still failing

What it is

Infisical at a glance

Infisical is an open-source secrets management platform offering a dashboard, CLI, SDKs, a Kubernetes operator and an agent. It supports environment and folder-scoped secrets, overrides per user or environment, and multiple authentication methods for workloads including Kubernetes service accounts and short-lived tokens.

The project is maintained by Infisical Inc. with a source-available licence for the core, a cloud-hosted service and a self-hostable Helm chart. Typical uses include teams that want the Doppler experience with the option to self-host, Kubernetes platforms that need secrets flowing from a central store, and organizations with compliance requirements that push them off third-party SaaS.

Type
Open-source secrets management platform
First released
2022
License
MIT core, enterprise features under proprietary terms
Maintained by
Infisical Inc.
Typically used for
Secret storage with Kubernetes delivery, environment overrides, self-hosted secrets management

The honest version

Infisical pros and cons

No technology is all upside. This is where Infisical earns its place and where it tends to cause trouble.

Where Infisical is strong

  • Self-hostable or cloudYou can run the whole stack on your own cluster under the MIT core or use the hosted service, and the API shape is the same either way, which lets teams move between the two without rewrites.
  • Kubernetes operator is first classInfisicalSecret and InfisicalPushSecret CRDs sync secrets into native Kubernetes Secret objects, so applications keep reading environment variables the normal way.
  • Multiple auth methods for workloadsKubernetes service account auth, GCP, AWS, Azure, universal and token-based auth cover most of the ways a workload actually proves who it is.
  • Overrides per user and environmentDevelopers can safely override secrets in dev without touching production values, which is the kind of workflow that otherwise drifts into private .env files.
  • Secret references across projectsA central project can hold shared secrets and other projects pull them in, so the same database password does not have to live in five configs.
  • Open-source gives an exitRunning it yourself is always available, so the decision to use the cloud service is a convenience rather than a lock-in you cannot reverse.

Where Infisical bites

  • Operator can stall quietlyRBAC that is too tight, a missing auth token, or a TokenReview the backend cannot perform leaves InfisicalSecret objects stuck in Pending with little indication beyond the operator pod logs.
  • Override semantics confuse teamsPersonal overrides are visible to the user who set them but not to the operator pulling shared values, which means a dev-only override that works locally does not land in a pod without specific configuration.
  • Self-hosting is non-trivialPostgres, Redis, migrations and Helm values each have to be managed, and upgrades across majors sometimes need an intermediate step rather than a straight apply.
  • Smaller ecosystem than larger vendorsFewer first-party integrations with deploy targets than long-established competitors, so some integrations end up as custom CI steps rather than a clickable connector.
  • Authentication surface is broadMany auth methods mean many ways to misconfigure, and a Kubernetes service account that cannot reach the backend produces the same error regardless of the real cause.
  • Audit and compliance features gatedSSO enforcement, audit log retention and some policy controls are only available on paid tiers, which turns a secrets project into a license conversation earlier than teams expect.

Sound familiar?

Common Infisical problems we fix

The Infisical problems that bring people to us, and what you have once each one is fixed.

no authentication method provided

Operator cannot authenticate to the backend

An InfisicalSecret manifest that references a Kubernetes Secret containing the Infisical token, with the Secret missing, in the wrong namespace, or holding a key name the operator does not recognise.

Auth reference pointed at the right Secret

InfisicalSecret stuck in Pending

Secret sync never starts

The operator queued a reconcile that cannot complete, usually because the cluster role is missing permission to create Secrets in the target namespace or the backend is unreachable.

Reconcile completing, Secret materialised

TokenReview failed with 403

Kubernetes Auth cannot verify the service account

The Infisical backend calling the Kubernetes TokenReview API with no permission to do so, or the cluster API server unreachable from the Infisical instance when running self-hosted.

TokenReview path open and authorized

override not applied

Personal overrides never reach the pod

An environment configured to use shared secrets only, with the operator pulling the shared value instead of the override, so a secret that a developer changed in the UI never appears in the running container.

Override resolution configured intentionally

InfisicalPushSecret conflict

Pushed secrets clash with existing values

A PushSecret targeting a Kubernetes Secret that already exists with the policy left at None, so the operator refuses to overwrite and the sync never lands.

Update policy chosen and applied

destination.projectSlug 'web' not found

The project or environment slug is wrong

A typo or a project rename that was not reflected in the manifest, with the operator failing to locate the destination and leaving the reconcile in error.

Project and environment slugs reconciled

self-hosted backend unreachable

Operator cannot reach a self-hosted backend

A NetworkPolicy, a missing egress rule or a backend behind an ingress with a cert the operator does not trust, so every reconcile fails without obvious cause in the CRD status.

Network path and trust restored

What we do

Infisical help, from rescue to tidy self-hosting

Call us for one stuck InfisicalSecret, or hand us the operator, the backend and the clusters that depend on them.

Rescue
Operators stuck Pending, TokenReview failing, or overrides that will not land in production. We get secrets syncing again before anything else.
Operator design
Service account auth, RBAC and namespace scoping arranged so the operator has what it needs and nothing more, with CRD examples that match the policy.
Self-hosted deployment
Helm values, Postgres, Redis, backups and upgrade path arranged so running Infisical yourself does not become its own operational burden.
Override and reference policy
Shared secrets, references and overrides laid out so personal values stay local and production stays predictable, with tests to prove it.
Migration from Doppler or Vault
Moving secrets between managers without losing integrations, with a staged cutover that keeps services running the whole time.
Managed Tech
Rotations exercised, operator health watched, upgrades tested on a scratch cluster, and a human to reach when the InfisicalSecret CRD stops reconciling in the middle of the night.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Infisical alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Infisical questions

Something else? Call+1 737 727 7327

Why is our InfisicalSecret stuck Pending?

Three common causes: the operator does not have RBAC to create Secrets in the target namespace, the authentication token referenced in the CRD is missing or in the wrong format, or the backend cannot be reached at all. The operator pod log usually shows which of those it is within a few seconds of the reconcile attempt.

How do overrides actually work?

Personal overrides are stored encrypted against your user account and only resolved when the fetcher is authenticated as you. An operator running in a cluster is not you, so it reads the shared value. To push a user override into a pod you need to switch the fetch method or treat the override as a shared secret in that environment.

Should we self-host Infisical?

If data residency, air-gapped environments or strict compliance pushes you off third-party SaaS, yes. If none of those apply, the hosted service is usually less work and the cost is reasonable at team sizes where secrets are a side project rather than the project.

Can Infisical replace Vault?

For environment secrets fetched by applications, yes. For dynamic database credentials, PKI, SSH CA and some of Vault's more specialised engines, not fully. Teams running both is a reasonable pattern, with Infisical for day-to-day secrets and Vault for the places where it specifically earns its keep.

How much does Infisical help cost?

The estimate is free of charge. Describe the operator, the backend and the problem you are chasing, and we come back with a price before we touch anything.

Free estimate

Infisical giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.