A collection of small, static cloud-native tools published with GitHub Pages.
Open /k8s-manifest-builder/ to configure an apps/v1 Deployment,
StatefulSet, or DaemonSet and export it as YAML or JSON.
The form covers common workload, container, probe, resource, storage, scheduling, security, lifecycle, and rollout fields. The Additional manifest fields editor accepts a JSON object that is deep-merged into the generated resource for API fields not represented directly in the form.
Open /visual-subnet-calculator/ to split an IPv4 CIDR block into a visual,
editable plan. Subnets can be split, joined, color-coded, annotated, exported
as JSON, or shared through a URL. Standard IPv4, AWS VPC, and Azure VNet
address reservation policies are supported.
Open /yaml-formatter/ to validate, format, and convert YAML or JSON
entirely in the browser. The editor auto-detects the input format, reports
syntax errors with line and column details, supports multi-document YAML, and
can copy or download the formatted result.
The shorter /json-formatter/ alias redirects to this tool.
YAML parsing and serialization use the vendored js-yaml 4.1.0 browser
bundle, distributed under the MIT license included with the tool.
Open /kubernetes-rbac-explorer/ to turn Kubernetes Roles and bindings into
an effective access map. The tool resolves subject-to-role grant paths, answers
permission questions, highlights review-worthy access, compares policy
snapshots, generates narrowly scoped RBAC drafts, and exports a Markdown review.
The explorer accepts multi-document YAML, JSON arrays, and Kubernetes List
objects. Parsing and analysis stay in the browser. Secret objects are rejected,
and users should never provide a kubeconfig, token, or other credentials. YAML
input uses the existing vendored js-yaml 4.1.0 bundle.
The random sample library demonstrates namespace read-only access, deployment operations, sensitive cluster access, RBAC administration, aggregated ClusterRoles, and incomplete policy exports. Consecutive sample selections do not repeat the same scenario.
Open /terraform-modules/ to explore public AWS Terraform modules
maintained by the native-cube GitHub organization. The catalogue covers Amazon
EKS, EKS Auto Mode, managed node groups, Fargate profiles, KMS, and VPC Flow
Logs, with direct links to each GitHub repository and Terraform Registry page.
Module names, descriptions, categories, complete-example paths, and visual
treatments are maintained in terraform-modules/modules.json. Registry
versions, release dates, required inputs, Terraform and AWS requirements,
licenses, and GitHub status are synchronized into the same file and used to
generate module cards, permalinks, starter snippets, and structured data.
Editors can use terraform-modules/modules.schema.json for autocomplete. CI
validates the catalogue against that schema and performs duplicate-name and
generated-output checks in the synchronization script.
Refresh live metadata and regenerate the page:
python3 scripts/sync-terraform-modules.py --writeRegenerate from local catalogue data without network access, or verify live data and committed HTML without changing files:
python3 scripts/sync-terraform-modules.py --render
python3 scripts/sync-terraform-modules.py --checkTo add a module, add its curated entry to modules.json, publish the matching
terraform-aws-<name> repository and Registry module, then run --write. Add
example_path only when the repository contains a complete maintained example.
The weekly catalogue workflow refreshes metadata and opens or updates a pull
request when anything changes. GitHub Actions must be permitted to create pull
requests in the repository or organization workflow settings.
The dedicated social card is maintained as an editable SVG. On macOS, regenerate its required 1200×630 PNG with:
sh scripts/render-social-card.shOther social cards can use the same renderer by supplying both paths, for example:
sh scripts/render-social-card.sh \
assets/social/kubernetes-rbac-explorer.svg \
assets/social/kubernetes-rbac-explorer.png## To preview locally
python3 -m http.server 8080http://localhost:8080/k8s-manifest-builder/http://localhost:8080/kubernetes-rbac-explorer/http://localhost:8080/visual-subnet-calculator/http://localhost:8080/yaml-formatter/http://localhost:8080/terraform-modules/
Run the repository SEO audit locally:
python3 scripts/seo-audit.pyThe Lighthouse and SEO GitHub Actions workflow audits every canonical page
on pull requests and pushes to main. It enforces minimum performance,
accessibility, best-practices, and SEO scores together with lab thresholds for
Largest Contentful Paint, cumulative layout shift, and total blocking time. It
also validates HTML and checks internal fragments and external links.
Google Search Console requires account-issued ownership verification. Follow
SEARCH_CONSOLE.md to add the URL-prefix property,
install the unmodified verification file, submit the sitemap, and request
indexing for each canonical page.