Configuration Guide

VM Network Configuration

Configure network settings for your GCM virtual machine using the automated configuration wizard.

Network Settings

You'll need to provide the following network information:

Manual Network Configuration

If you need to configure networking manually:

nmcli con mod ens192 ipv4.addresses 192.168.1.10/24
nmcli con mod ens192 ipv4.gateway 192.168.1.1
nmcli con mod ens192 ipv4.dns '192.168.1.2 8.9.9.9'
nmcli con mod ens192 ipv4.method manual
nmcli con up ens192

Hostname & DNS Configuration

Set the hostname and FQDN for your GCM system.

Hostname Components

Set Hostname

hostnamectl set-hostname gcm-prod.company.com

Verify Hostname

hostnamectl
hostname
hostname -f

Time & NTP Configuration

Configure timezone and NTP synchronization for accurate timekeeping.

Set Timezone

# List available timezones
timedatectl list-timezones

# Set timezone
timedatectl set-timezone America/New_York

Configure NTP

# Enable NTP
timedatectl set-ntp true

# Configure NTP server (optional)
echo 'server ntp.company.com iburst' >> /etc/chrony.conf
systemctl restart chronyd

# Verify time sync
timedatectl status
chronyc sources

Firewall Configuration

Configure firewall rules to allow access to GCM services.

Required Ports

Configure Firewall

# Open required ports
firewall-cmd --permanent --add-port=30443/tcp
firewall-cmd --permanent --add-port=31443/tcp

# Reload firewall
firewall-cmd --reload

# Verify rules
firewall-cmd --list-all

GCM Sizing Models

Choose the appropriate sizing model based on your workload requirements.

Configure Sizing

The configuration wizard will prompt you to select a sizing model:

./02-configure_gcm.sh

Storage Configuration

GCM requires specific storage classes for application and database storage.

Storage Options

Required Storage Classes

GCM requires TWO storage classes:

Verify Storage Classes

export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
kubectl get storageclass

Platform Versions

GCM 2.0.1 has been validated with specific platform versions.

Advanced Configuration Options

Additional configuration options for advanced deployments.

Custom Registry

Use a private container registry:

# Edit configuration
vi /etc/gcm/gcm-config.env

# Set custom registry
CONTAINER_REGISTRY=registry.company.com

Custom Storage Classes

Specify custom storage class names:

# Edit configuration
vi /etc/gcm/gcm-config.env

# Set custom storage classes
STORAGE_CLASS_FS=my-filesystem-class
STORAGE_CLASS_BLOCK=my-block-class

Resource Limits

Adjust resource limits for GCM pods:

# Edit GCM values
vi /root/gcm-values.yaml

# Adjust resource limits
resources:
  limits:
    cpu: 4000m
    memory: 8Gi
  requests:
    cpu: 2000m
    memory: 4Gi

Verify Configuration

Validate your configuration before proceeding with installation.

Run Validation Script

./03-validate_config.sh

Manual Verification

View Configuration

# View VM configuration
cat /etc/gcm/vm-config.env

# View GCM configuration
cat /etc/gcm/gcm-config.env

Access GCM After Installation

Once installation is complete, access your GCM instance.

GCM URLs

Default Credentials

# Get admin password
kubectl get secret gcm-admin-secret -n gcm -o jsonpath='{.data.password}' | base64 -d

Backup Configuration

Backup your configuration files for disaster recovery.

Configuration Files to Backup

• /etc/gcm/vm-config.env - VM network configuration
• /etc/gcm/gcm-config.env - GCM application configuration
• /root/gcm-values.yaml - GCM Helm values
• /etc/rancher/k3s/k3s.yaml - Kubernetes config

Create Backup

# Create backup directory
mkdir -p /root/gcm-backup-$(date +%Y%m%d)

# Backup configuration files
cp /etc/gcm/*.env /root/gcm-backup-$(date +%Y%m%d)/
cp /root/gcm-values.yaml /root/gcm-backup-$(date +%Y%m%d)/
cp /etc/rancher/k3s/k3s.yaml /root/gcm-backup-$(date +%Y%m%d)/

# Create tarball
tar -czf /root/gcm-backup-$(date +%Y%m%d).tar.gz /root/gcm-backup-$(date +%Y%m%d)/

Next Steps