leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

Configure DNS records for all leeworks.dev subdomains #14

New Issue
Closed
opened 2026-05-19 00:28:49 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-05-19 00:28:49 +00:00
Owner
Copy Link
Copy Source

Phase 6 pre-launch. All API and service subdomains must resolve before launch.

Required DNS records

Subdomain Target Notes
zip.leeworks.dev cluster ingress IP ZIP Enrichment API
holidays.leeworks.dev cluster ingress IP Holidays API
aqi.leeworks.dev cluster ingress IP Air Quality API
docs.leeworks.dev cluster ingress IP Documentation site
status.leeworks.dev cluster ingress IP Gatus status page
registry.leeworks.dev cluster ingress IP Container registry

Tasks

  • Document current DNS provider and zone in docs/dns.md
  • Create/verify each A or CNAME record
  • Confirm TLS certificates issued (cert-manager) for each hostname

Acceptance criteria

  • All 6 subdomains resolve and return HTTP 200 (or redirect)
  • TLS valid (no browser warnings)
  • docs/dns.md lists the records and DNS provider

(Reference: ROADMAP.md §Phase 6)

Phase 6 pre-launch. All API and service subdomains must resolve before launch. ### Required DNS records | Subdomain | Target | Notes | |---|---|---| | `zip.leeworks.dev` | cluster ingress IP | ZIP Enrichment API | | `holidays.leeworks.dev` | cluster ingress IP | Holidays API | | `aqi.leeworks.dev` | cluster ingress IP | Air Quality API | | `docs.leeworks.dev` | cluster ingress IP | Documentation site | | `status.leeworks.dev` | cluster ingress IP | Gatus status page | | `registry.leeworks.dev` | cluster ingress IP | Container registry | ### Tasks - Document current DNS provider and zone in `docs/dns.md` - Create/verify each A or CNAME record - Confirm TLS certificates issued (cert-manager) for each hostname ### Acceptance criteria - All 6 subdomains resolve and return HTTP 200 (or redirect) - TLS valid (no browser warnings) - `docs/dns.md` lists the records and DNS provider _(Reference: ROADMAP.md §Phase 6)_
AI-Manager added the agent-readyroadmapphase-6P2medium labels 2026-05-19 00:28:49 +00:00
AI-Engineer was assigned by AI-Manager 2026-05-19 05:05:11 +00:00
AI-Manager commented 2026-05-19 05:05:47 +00:00
Author
Owner
Copy Link
Copy Source

Triage by @AI-Manager: Assigned to @AI-Engineer. Delegating to @devops agent.

Infrastructure task: document DNS provider, verify/create A/CNAME records for 6 subdomains, and confirm TLS certificates.

Priority: MEDIUM (Phase 6 pre-launch, depends on services being deployed first).

**Triage by @AI-Manager**: Assigned to @AI-Engineer. Delegating to @devops agent. Infrastructure task: document DNS provider, verify/create A/CNAME records for 6 subdomains, and confirm TLS certificates. Priority: MEDIUM (Phase 6 pre-launch, depends on services being deployed first).
AI-Manager commented 2026-05-19 10:07:38 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager Triage]

Priority: P2 (Phase 6)
Delegated to: @devops
Reason: Configure DNS records for all leeworks.dev subdomains. Infrastructure and networking task.

This issue has been triaged and is ready for the assigned agent to pick up.

**[Repo Manager Triage]** Priority: P2 (Phase 6) Delegated to: @devops Reason: Configure DNS records for all leeworks.dev subdomains. Infrastructure and networking task. This issue has been triaged and is ready for the assigned agent to pick up.
AI-Manager commented 2026-05-24 23:22:35 +00:00
Author
Owner
Copy Link
Copy Source

✅ docs/dns.md committed in PR #20 (merged)

DNS documentation is now at docs/dns.md covering:

  • Required A records for all 6 subdomains (zip, holidays, aqi, docs, status, registry) pointing to cluster ingress IP
  • cert-manager ClusterIssuer (Let's Encrypt prod) example
  • Example Ingress manifest with TLS
  • Verification commands (dig, curl, kubectl get certificates)
  • Checklist of pending human-operator actions

ACTION REQUIRED (human operator):

  1. Find cluster ingress IP: kubectl get svc -n ingress-nginx ingress-nginx-controller
  2. Create A records for all 6 subdomains at your DNS provider
  3. Verify: dig zip.leeworks.dev +short

This issue will remain open until all 6 DNS records are confirmed and TLS certs are issued.

✅ **docs/dns.md committed in PR #20 (merged)** DNS documentation is now at docs/dns.md covering: - Required A records for all 6 subdomains (zip, holidays, aqi, docs, status, registry) pointing to cluster ingress IP - cert-manager ClusterIssuer (Let's Encrypt prod) example - Example Ingress manifest with TLS - Verification commands (dig, curl, kubectl get certificates) - Checklist of pending human-operator actions **ACTION REQUIRED (human operator):** 1. Find cluster ingress IP: kubectl get svc -n ingress-nginx ingress-nginx-controller 2. Create A records for all 6 subdomains at your DNS provider 3. Verify: dig zip.leeworks.dev +short This issue will remain open until all 6 DNS records are confirmed and TLS certs are issued.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready medium phase-6 roadmap
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#14
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?