ASTRONOMER PRODUCT / GOVERNANCE & ACCESS

One access model for the whole fleet.

Decide who can do what, on which clusters and namespaces, from one place. Connect the identity provider you already run, give teams bounded projects on shared clusters, and keep a record of the actions that matter.

Alpha · SSO requires the bundled Dex tool · presets are not certifications

01 / PROJECTS

Shared clusters, bounded teams.#

A project groups namespaces across clusters and gives a team its own members, quotas, policy, catalogs and cloud credentials. Platform teams hand out capacity without handing out the whole cluster.

  • CPU, memory and pod-count quotas, with usage shown against them
  • A project policy matrix for pod security and network policy posture
  • Project-scoped catalogs and cloud credentials for AWS, GCP, Azure, DigitalOcean or generic credentials
  • Delivery sources and targets belong to a project
PROJECTASTRONOMER
Project: A project with its clusters, namespaces and role bindings, and sections for quota, policy, catalogs and cloud credentials.Project: A project with its clusters, namespaces and role bindings, and sections for quota, policy, catalogs and cloud credentials.
A project with its clusters, namespaces and role bindings, and sections for quota, policy, catalogs and cloud credentials.

02 / RBAC

Grant at the right scope. See the result.#

Roles are granted globally, on a project, on a cluster or on a namespace. The console is permission-aware, so people see the actions they can take. The effective-permission view explains every grant a person holds and the binding it came from.

ACCESS ADMINISTRATION
Roles & effective access: Users, global, cluster and project roles, role bindings and effective permissions.Roles & effective access: Users, global, cluster and project roles, role bindings and effective permissions.
Users, global, cluster and project roles, role bindings and effective permissions.
ROLES

Custom and curated

Create, edit, duplicate and delete custom roles, or apply curated project-role templates.

ENFORCED

Before the agent

Authorization and tenant scoping are invariants, checked before a request reaches a cluster. Missing authorization fails closed.

DIRECTORY

Audited lookups

Directory search for assigning people is audited. Pre-login discovery works with LDAP connectors; others say it is unsupported rather than guessing.

03 / IDENTITY

Bring your identity provider.#

Single sign-on runs through Dex, installed and configured from Astronomer. Map identity-provider groups to Astronomer roles, and provision users and groups with SCIM.

CONNECTORS

Dex single sign-on

Generic OIDC, Okta, Microsoft Entra ID, GitHub, GitLab, Bitbucket Cloud, Google Workspace, SAML 2.0, LDAP or Active Directory, and generic OAuth.

PROVISION

SCIM and groups

SCIM Users and Groups with scoped SCIM tokens, plus group mappings from your provider to Astronomer roles.

LOCAL

Local accounts

Email sign-in with HttpOnly session cookies, password policy, lockout, TOTP with recovery codes and session revocation.

AUTOMATION

Scoped API tokens

Automation uses revocable, scoped API tokens, not credentials lifted from a browser session.

Dex is off by default in the management Helm chart; enable it to use SSO connectors. Upstream identity-provider availability is outside Astronomer.

04 / AUDIT

A record of the actions that matter.#

Astronomer records material reads, writes, secret access, service proxy mutations, shell sessions, delivery operations, RBAC changes and administrative actions. Recording a change’s intent is fail-closed: if the audit record cannot be written, the change does not proceed.

Audit events leave through a durable outbox, so a worker restart does not drop them. Read-audit policies add scrutiny to sensitive reads, and events forward to your SIEM over syslog, Splunk HEC or NDJSON HTTPS.

  • Search, filter and export the log
  • Secret values are redacted from audit details
  • Configurable retention, guarded against silent downgrade by presets

Not every domain change writes its audit row in the same database transaction yet. Monitor receipt at your SIEM.

AUDIT LOGASTRONOMER
Audit log: The audit log: search events and filter by event class and result, with correlation IDs to follow one request.Audit log: The audit log: search events and filter by event class and result, with correlation IDs to follow one request.
The audit log: search events and filter by event class and result, with correlation IDs to follow one request.

05 / COMPLIANCE PRESETS

Apply a baseline in one transaction.#

Settings › Compliance › Baselines applies a preset to audit retention, the Pod Security profile, two-factor and email settings, quota plans and templates. The previous values are captured first, so an application can be reverted. A preset that would shorten audit retention is refused.

Compliance presets and what they set
PresetAudit retentionPod Security profileTOTP required
PCI DSS 4.0365 daysrestrictedyes
HIPAA2,190 daysrestrictedyes
FedRAMP Moderate1,095 daysrestrictedyes
SOC 2 (Type II)365 daysbaselineno

Not a certification

Presets configure Astronomer. They do not certify a deployment, and the FedRAMP Moderate preset does not claim FedRAMP authorization or FIPS validation.

FAQ

Access questions.#

Do Astronomer roles become Kubernetes RBAC on the cluster?

Astronomer checks its own grants before a request reaches the agent. For the browser shell, it renders a short-lived Kubernetes role that is the intersection of the requested access and your grants. Namespace-scoped behavior depends on what the operation and agent can enforce. #

Can we manage projects as code?

Yes. With the optional CRDs enabled, a Project resource under management.astronomer.io/v1alpha1 declares project policy, quotas, network-policy and pod-security posture and cluster membership. REST and UI changes cannot silently overwrite CRD-owned fields. #

Can auditors get read-only access?

Grant a role with read permissions only, at the scope they need. Read-audit policies can record what they look at. #

NEXT STEP

Review the access model with your team.

Bring your identity provider, tenancy model and audit requirements. We will map them to Astronomer.

Find your next step

13 pages

Tab through results · Enter to open · Escape to close