Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

deploy/k8s: polish follow-ups from the slice 1 reviews

Open
#435 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, eslint, kubernetes, typescript

Research direction

Start by reading the checklist and the named files: deploy/k8s/overlays/ocp/kustomization.yaml, deploy/k8s/base/control-plane.yaml, the kind-ci mock-model manifest, deploy/k8s/README.md, deploy/vm/env/supervisor.env.example, redactUrl, and render.ts. Check nearby conventions and run the relevant Kubernetes validation and lint checks. Done means all seven review follow-ups are addressed without changing the documented behavior.

Written by the indexing model from the issue text.

Description

enhancement

Small polish items from the task reviews of #427 (P6 on Kubernetes slice 1).

  • Smaller ghostunnel image: pin docker.io/ghostunnel/ghostunnel:v1.11.3-distroless (re-resolving the digest) instead of the default Alpine variant (deploy/k8s/overlays/ocp/kustomization.yaml).
  • Inert setting: SH_SANDBOX_NAMESPACE in deploy/k8s/base/control-plane.yaml has no effect without the pods Role. Drop it, or comment it.
  • kind-ci mock-model sidecar: add /tmp (an emptyDir), HOME=/tmp and a tcpSocket probe on 18099, to match the brain-container convention.
  • redactUrl doc: note that URL.toString() normalises the URL (for example lowercasing the host), so the redacted output can differ from the input in more than the userinfo.
  • deploy/vm/env/supervisor.env.example: wrap the SH_ADMIN_HOST comment to the template's line width.
  • deploy/k8s/README.md §9.5: each session delete answers 204, or 202 if a turn is in flight. The session loop reads only the first page (?limit= or loop on nextCursor).
  • render.ts: move the eslint-disable-next-line comment directly above the any line.
Dominant language
TypeScript
Stars
4
Forks
9
Avg merge
9h 31m
Merged PRs (30d)
139

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rossoctl/moca

All issues in rossoctl/moca

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.