Frequently Asked Questions (FAQ)
Here are answers to commonly asked questions when using the KIWI platform.
Getting Started
Q. I'm using KIWI for the first time. How do I get started?
A. Follow these steps to get started with KIWI:
- Register the server you want to manage on the [Device Management] page
- Connect a K8s cluster or Docker runtime on the [Runtime Environment] page
- Link a Git repository on the [Service Management] page
- Complete build and deployment configuration .
For more details: System Registration Scenario
Q. What permissions do I need?
A. KIWI uses the following permission structure:
device: [Device Management] - Server/device managementinfra: [Runtime Environment] - K8s/Docker environment managementservice: [Service Management] - Service build/deploymentbackup: [Backup Management] - Backup/restore operationsdatabase: [Database Management] - Database managementaudit: [Audit Log] - Log viewing
Request permissions from an administrator on the [Permission Management] page.
Device Management
Q. Server connection test is failing.
A. Please check the following:
- Network check: Verify that the server IP is accessible .
- SSH port check: If using a port other than the default (22), enter it correctly .
- Firewall check: Verify that the SSH port is allowed in the firewall
- Authentication check: Verify SSH username and password (or SSH private key)
Related page: [Device Management]
Q. How do I register a server that requires access through a gateway?
A. KIWI supports multi-hop SSH:
- Register the gateway server first on the [Device Management] page
- When registering internal servers, select the gateway server as the parent device .
- Enter internal server information (private IP, port)
Runtime Environment
Q. How do I connect an external Kubernetes cluster?
A. Follow these steps:
- Go to the [Runtime Environment] page
- Click the "Import External Runtime" button .
- Upload kubeconfig file or enter it directly .
- Test the connection and save .
Note: kubeconfig must contain a valid token.
For more details: System Registration Scenario
Q. Docker runtime is not connecting.
A. Please check the following:
- Docker daemon check:
systemctl status docker - Socket permission check: Verify that the user belongs to the docker group
- Remote API settings: If using TCP socket, check
/etc/docker/daemon.jsonconfiguration .
Related page: [Runtime Environment]
Service Management
Q. Git repository connection is failing.
A. Please check the following:
- URL format: HTTPS URL is recommended (
https://gitlab.com/...) - Token permissions: Personal Access Token needs
read_repositorypermission . - Token expiration: Check token validity period
Related page: [Service Management]
Q. Build is failing. How do I check it?
A. Follow these steps when a build fails:
- [Service Management] → Select service → Build tab
- Check the log of the failed build
- Common causes:
- Dockerfile syntax error
- Base image not accessible .
- Dependency installation failure
- Registry authentication failure
Q. Image push is failing.
A. Please check the following:
- Registry URL: Verify the correct registry address .
- Authentication credentials: Check registry login information .
- Project permissions: Verify push permissions for the project in the registry .
- Image tag: Use the correct tag format
Related page: [Service Management]
Security Scanning
Q. SAST scan results are not appearing.
A. Please check the following:
- Supported languages: Verify that CodeQL/Semgrep supports the language
- Repository size: Large repositories may take longer to scan
- Source code location: Verify that source code is in the root directory .
Related page: [Service Management] → Security tab
For more details: Security Scan Setup Scenario
Q. Too many vulnerabilities appear in SCA scan.
A. Use the VEX filter:
- [Service Management] → Select service → Security tab
- Enable "VEX Filter" in SCA results .
- Vulnerabilities that don't actually affect you will be automatically filtered .
You can also set exception policies to ignore specific vulnerabilities.
Q. How do I download SBOM?
A. Follow these steps:
- [Service Management] → Select service → Security tab
- Click "Generate SBOM" button .
- Select source SBOM or image SBOM
- Download in CycloneDX or SPDX format
For more details: Security Scan Setup Scenario
Deployment
Q. Pod does not start after deployment.
A. Please check the following:
- Image pull: Verify that the image is pulled correctly .
- Resource limits: Check that CPU/memory limits are not too low
- Environment variables: Verify that required environment variables are set
- Port configuration: Verify that container port is configured correctly .
Debugging method:
kubectl describe pod <pod-name> -n <namespace>
kubectl logs <pod-name> -n <namespace>
Q. Cannot access the deployed service.
A. Please check the following:
- Service configuration: Verify ClusterIP/LoadBalancer/NodePort
- Ingress configuration: Check Ingress rules and domain settings .
- Network policy: Verify that traffic is not blocked by NetworkPolicy
Backup Management
Q. How do I create a backup?
A. Follow these steps:
- Go to the [Backup Management] page
- Click "Create Backup" button .
- Select backup target (etcd, database, PVC, etc.)
- Select backup storage (local, MinIO, external storage)
- Execute backup
Q. How do I restore from a backup?
A. Follow these steps:
- Go to the [Backup Management] page
- Select the backup to restore
- Click "Restore" button .
- Verify restore target and execute .
Warning: Restore will overwrite existing data. Proceed with caution.
Permissions and Users
Q. How do I invite a new user?
A. Manager permission or higher is required:
- Go to the [User Management] page
- Click "Invite User" button .
- Enter email and select role .
- Send invitation
Q. How do I change user permissions?
A. Manager permission or higher is required:
- Go to the [Permission Management] page
- Select the user to change permissions .
- Check/uncheck required permissions .
- Save
Troubleshooting
Q. Screen is stuck on loading.
A. Try the following:
- Refresh browser (Ctrl+F5)
- Clear browser cache
- Try with a different browser .
- Check network connection .
If the problem persists, contact an administrator.
Q. An error message is displayed.
A. Check the error message and refer to the following:
- 401 Unauthorized: Login expired → Log in again
- 403 Forbidden: Insufficient permissions → Request permissions from administrator
- 404 Not Found: Resource not found → Check URL and resource existence .
- 500 Internal Error: Server error → Contact administrator
Additional Help
For more detailed information, refer to the following documentation:
System Configuration
- System Registration Scenario - Register server, K8s, Docker .
- Service Registration Scenario - Git integration, build configuration .
Build and Deployment
- Build/Deploy Scenario - CI configuration, container build, deployment .
- Security Scan Setup Scenario - SAST, SCA, DAST configuration .
Operations Management
- Backup/Restore Scenario - etcd, Docker backup/restore
- Database Management Scenario - Database connection, synchronization .
Administrator Functions
- User/Permission Management Scenario - User invitation, permission settings .
- VPN Settings Scenario - VPN profile management .
- Audit Log Scenario - Log viewing, filtering .