Read only cluster role for Lens read only users

100%

Read only cluster role for Lens read only users

✓ Published0🌍 Public

Last edited Jan 27, 2022

Created on Jan 27, 2022

This example visualizes a Kubernetes RBAC configuration by defining a `ClusterRole` named `read-only-clusterrole` for Lens read-only users. It shows the explicit mapping of permitted API groups, resources, and HTTP verbs—using `get`, `list`, and `watch`—across a broad set of Kubernetes object types. The YAML file enumerates resources such as pods, deployments, services, and custom endpoints, specifying non-resource URLs like `/metrics`. The code relies on the Kubernetes RBAC API schema to structure permissions, rendering a declarative security policy that restricts access to read-only operations. This illustrates how fine-grained access control is encoded using YAML syntax within a Kubernetes cluster role definition.

AI-generated description

Similar vizzes

Loading thumbnail…

s3 lambda permission

This visualization shows the AWS Identity and Access Management (IAM) permissions required for an S3 bucket used by a Lambda function. It displays the policy structure, including the `s3:*` action and the bucket ARN as the resource, using a hierarchical tree layout. The code employs D3.js (likely `d3.hierarchy` and `d3.tree`) to render the JSON policy as connected nodes, with the root representing the policy object and branches for the action, effect, and resource arrays. The data comes directly from the gist’s static JSON configuration.

66ewis

46% match

Loading thumbnail…

Copy kubernetes secrets between namespaces

This example demonstrates a shell one-liner that copies Kubernetes secrets from one namespace to another. It uses `kubectl get secrets` with JSON output to retrieve the source secrets, then pipes the result through `jq` to rewrite the `metadata.namespace` field to the target namespace. The transformed JSON is applied directly with `kubectl apply -f -`. The visualization highlights the command pipeline’s data flow, relying on the Kubernetes CLI and jq for JSON manipulation, with no additional charting or rendering libraries involved.

TThanad

45% match

Loading thumbnail…

lf-auth-notes

This interactive visualization demonstrates how cryptographic keys and team membership are managed in a decentralized graph, where each node is an encrypted lockbox containing keys accessible only to designated devices or roles. It shows the flow of authority from the group’s founder through admin roles to individual members, with mutual removals resolved by seniority. Built on the CRDX library, the graph uses asymmetric encryption for each node, and the visualization renders the key graph and lockbox relationships using custom SVG rendering. The code highlights the concrete APIs for graph traversal and cryptographic operations, such as key derivation and signature verification, as seen in the invitation and lockbox logic. Data is sourced from the embedded gist’s markdown and assets.

HHerbCaudill

45% match

Loading thumbnail…

Radar chart

This radar chart visualizes cluster data from a CSV file, comparing multiple financial metrics across five clusters. Each cluster is represented as a filled polygon overlaid on a web of axes, with angular rings showing value levels. The chart uses D3.js v3 with SVG rendering and hover interactions that highlight a selected cluster by reducing the opacity of others. Axes and labels are drawn from the dataset columns, and the polygons are built using D3’s data join and `transition` for smooth opacity changes.

MMohamedZaki

43% match

Loading thumbnail…

auth@next notes

This visualization maps the hierarchical and membership structure of an authentication system, showing how entities like teams, roles, users, and devices nest and connect. It uses a force-directed graph layout, likely via D3's `forceSimulation`, to position nodes by their relationships, with links drawn as curved paths. The data comes from TypeScript type definitions that model each entity with an `id`, `name`, keyset, and optional `members` array, revealing the recursive, tree-like organization of permissions. The rendering emphasizes the flow of access rights from high-level groups down to leaf agents and devices.

HHerbCaudill

43% match

Loading thumbnail…

Rook v0.8.0 device/osd removal

This example visualizes the seven-stage process of removing a failed OSD from a Rook v0.8.0 Ceph cluster, using osd.5 as a concrete walkthrough. It diagrams each command—from `ceph osd out` through `ceph osd rm` and Kubernetes deployment deletion—as sequential steps in a flowchart. The code renders this workflow with d3.forceSimulation for node positioning and d3.selector for interactive highlighting. The data source is a gistfile containing the step-by-step troubleshooting and recovery commands, showing both the failure path and the subsequent OSD recreation after new disk insertion.

TThanad

42% match

Loading thumbnail…

Gist cb2cc8b6e09fea8880fbaeca47c59dca

This example demonstrates a shell script that configures group-based file permissions for a web-served directory named "kirby". It shows the step-by-step process of changing ownership to the `www-data` group and applying specific read/write/execute modes for directories and files, while also setting the setgid bit and default access control lists via `setfacl`. The second half of the script condenses these commands into a single chained operation using `&&`, illustrating an alternative approach with the same outcome.

SSamuelRiversMoore

42% match

Loading thumbnail…

Gist 1e2285c06f37b9f31fb66bc361792ef1

This visualization displays a containerized task definition for an AWS ECS Fargate service, outlining the execution and task IAM roles, network configuration, and resource allocation. The code shows a Python-based container image with environment variables for mode, email, and password, using a custom entry point. It highlights the JSON structure for configuring a single container with command arguments, working directory, and port mappings, while specifying Fargate compatibility, CPU, and memory limits. The example illustrates how infrastructure-as-code defines serverless compute settings through a declarative task role and execution role setup.

CConorAspell

40% match