Skip to content

post-configuration.md

Latest commit

 

History

History
192 lines (125 loc) · 4.54 KB

post-configuration.md

File metadata and controls

192 lines (125 loc) · 4.54 KB

Post-Configuration

After your cluster is bootstrapped, this guide covers verification, accessing services, and initial configuration. These steps are the same for all providers.

Step 1: Verify Cluster Health

Check Cluster Status

export KUBECONFIG=./outputs/kubeconfigs/main.yaml

# Verify cluster info
kubectl cluster-info

# Check all nodes are ready
kubectl get nodes

# Check all system pods are running
kubectl get pods -A

Expected Output

All nodes should show Ready status and all pods should be Running or Completed.

Step 2: Access Dashboards

KubeAid deploys several web interfaces for managing and monitoring your cluster.

ArgoCD Dashboard

ArgoCD provides GitOps-based application management.

# Get ArgoCD URL
kubectl get ingress -n argocd

# Get admin password (if not set in secrets.yaml)
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d

Default credentials:

  • Username: admin
  • Password: Set in your secrets.yaml or retrieve from the secret above

Grafana Dashboard

Grafana provides monitoring dashboards powered by Prometheus.

# Get Grafana URL
kubectl get ingress -n monitoring

# Get admin password
kubectl -n monitoring get secret kube-prometheus-stack-grafana -o jsonpath="{.data.admin-password}" | base64 -d

Prometheus

Access Prometheus directly for metrics and alerting configuration:

kubectl get ingress -n monitoring

Step 3: Verify Core Components

Check ArgoCD Applications

kubectl get applications -n argocd

All applications should show Healthy and Synced status.

Check Cilium CNI

kubectl -n kube-system get pods -l k8s-app=cilium
kubectl -n kube-system exec -it ds/cilium -- cilium status

Check Sealed Secrets Controller

kubectl get pods -n kube-system -l name=sealed-secrets-controller

Step 4: Configure DNS (If Applicable)

If you're using custom domains for your cluster services, configure DNS records to point to your ingress load balancer:

# Get the external IP/hostname of your ingress
kubectl get svc -n ingress-nginx

Create DNS records (A or CNAME) for:

  • argocd.your-domain.com
  • grafana.your-domain.com
  • prometheus.your-domain.com

Step 5: Secret Management

KubeAid uses Sealed Secrets for secure secret management. Secrets are encrypted client-side and stored in Git.

Create a Sealed Secret

# Create a regular secret
kubectl create secret generic my-secret \
  --from-literal=username=myuser \
  --from-literal=password=mypassword \
  --dry-run=client -o yaml > my-secret.yaml

# Seal the secret
kubeseal --format yaml < my-secret.yaml > my-sealed-secret.yaml

# Apply the sealed secret
kubectl apply -f my-sealed-secret.yaml

Where Secrets Are Stored

Sealed secrets should be committed to your kubeaid-config repository:

k8s/<cluster-name>/sealed-secrets/<namespace>/<secret-name>.json

Step 6: Configure Updates

To receive feature and security updates for KubeAid:

Option A: Automatic Updates (Recommended)

Grant write access to your repositories to the GitHub user obmondo-pushupdate-user.

Option B: Manual Updates

Pull updates manually from the upstream KubeAid repository:

cd /path/to/your/kubeaid-fork
git remote add upstream https://github.com/Obmondo/KubeAid.git
git fetch upstream
git merge upstream/main
git push origin main

Provider-Specific Notes

Hetzner HCloud

Storage Limitation: HCloud storage only allows a maximum of 16 buckets (PersistentVolumes) per physical node. Monitor PV usage to avoid exhausting storage before node resources.

Azure

If using Azure Workload Identity, verify the webhook is functioning:

kubectl get pods -n azure-workload-identity-system

AWS

Verify Kube2IAM is properly configured for pod IAM credentials:

kubectl get pods -n kube-system -l app=kube2iam

Troubleshooting

Common Issues

Issue Solution
Nodes not ready Check kubelet logs: kubectl describe node <node-name>
Pods stuck in Pending Check for resource constraints: kubectl describe pod <pod-name>
ArgoCD apps not syncing Check ArgoCD logs: kubectl logs -n argocd deployment/argocd-application-controller
Network issues Check Cilium status: kubectl -n kube-system exec -it ds/cilium -- cilium status

Log Locations

  • Bootstrap logs: outputs/.log
  • Kubeconfig: outputs/kubeconfigs/clusters/main.yaml
  • Configuration files: outputs/configs/