AI Namespace - ArgoCD Managed

This directory contains Kubernetes manifests for the ai namespace.

🔄 ArgoCD Integration

All YAML files in this directory are automatically deployed to the K3s cluster by ArgoCD.

📝 Adding New Applications

Create your Kubernetes manifest files (deployment, service, ingress, etc.)
Place them in this directory
Commit and push to Git
ArgoCD will automatically detect and deploy the changes

🏷️ Namespace

All resources in this directory will be deployed to the ai namespace.

📋 Examples

Deployment Example

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-ai-app
  namespace: ai
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-ai-app
  template:
    metadata:
      labels:
        app: my-ai-app
    spec:
      containers:
      - name: my-ai-app
        image: my-image:latest
        ports:
        - containerPort: 8080

Service Example

apiVersion: v1
kind: Service
metadata:
  name: my-ai-app
  namespace: ai
spec:
  selector:
    app: my-ai-app
  ports:
  - port: 80
    targetPort: 8080

Ingress Example

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-ai-app
  namespace: ai
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  ingressClassName: nginx
  tls:
  - hosts:
    - myapp.junv.cc
    secretName: myapp-tls
  rules:
  - host: myapp.junv.cc
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: my-ai-app
            port:
              number: 80

🔐 Service Account

The ai-bot service account (on 192.168.1.10) has full access to this namespace for management and automation tasks.

ArgoCD Dashboard: https://argo.junv.cc
Service Account Setup: See /k8s/ directory for ai-bot configuration
Domain: *.junv.cc with automatic TLS via cert-manager

⚠️ Important Notes

Always specify namespace: ai in your manifests
Use cert-manager annotations for automatic TLS certificates
Follow the existing naming conventions for consistency
Test manifests locally before committing when possible

Last Updated: February 13, 2026

2.2 KiB Raw Blame History