We’re integrating Tectonic with Red Hat OpenShift

We are bringing the best of Tectonic to Red Hat OpenShift to build the most secure, hybrid Kubernetes application platform.

Role-Based Access Control

Tectonic Identity uses Kubernetes' integrated Role-Based Access Control (RBAC) to manage user roles and permissions within Tectonic clusters.

Use Tectonic Console to define Roles which grant a set of permissions to Accounts through Role Bindings.

By default, Tectonic offers three account types, and two Role and Role Binding types:

Account types:

  • User
  • Group
  • Service Account

Role types:

  • Roles: Restrict associated rules to a namespace.
  • Cluster Roles: Grant associated Rules across a cluster.

Role Binding types:

  • Namespace Role Binding: Defines namespace-specific permissions for users or a group of users.
  • Cluster-wide Role Binding: Defines cluster-wide permissions for users or a group of users.

A Role Binding can reference both Roles and Cluster Roles to grant permissions to resources. This allows administrators to define a set of common Roles for the entire cluster, then reuse them within multiple namespaces.

For example, creating a Role Binding in the dev namespace that binds a user to the edit Cluster Role won't have any impact outside of the dev namespace, even though it references a Cluster Role.

An attempt to access a resource or perform a command not allowed by the user's defined permissions will be rejected by the API server.

For more information on User Authentication and access management, see Creating Accounts, and Creating Roles.

Configuring RBAC

RBAC may be configured using Tectonic Console or kubectl. The following example creates two YAML files to define a Role and a Role Binding for user Jane Doe, which grants her basic access to the cluster.

  1. First, create a YAML file which defines the role support-readonly that can run commands get, logs, list, and watch for namespaces and pods:
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
  name: support-readonly
- apiGroups:
  - ""
  attributeRestrictions: null
  - namespaces
  - namespaces/finalize
  - namespaces/status
  - pods
  - get
  - logs
  - list
  - watch
  1. Then, bind the role to jane.doe's group tstgrp:
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
  name: support-reader
  namespace: kube-system
  - kind: Group
    name: tstgrp
  kind: ClusterRole
  name: support-readonly
  apiGroup: rbac.authorization.k8s.io

Tectonic Console and kubectl now reflect the updated role and binding: