Updating Octostar

Keep your Octostar installation up-to-date with the latest features and security patches

Overview

Updating Octostar is a straightforward process that ensures you have the latest features,performance improvements, and security patches. The update process is designed to be safeand minimally disruptive to your operations.

Estimated Time5-10 minutes
DowntimeMinimal
Risk LevelLow

Choose Your Update Track

Octostar offers two update tracks to suit different operational needs:

Stable Track

Recommended for production environments. Thoroughly tested and battle-hardened releases with extensive QA testing and monthly release cycles. Best for mission-critical deployments.

Download stable.yml →

Nightly Track

Early access to cutting-edge features. Best for development and testing environments with continuous integration and daily builds. Stay on the bleeding edge.

Download nightly.yml →

Update Procedure

Step 1: Backup Current Configuration

Before updating, always backup your current versions.yml file. This allows you to rollback quickly if needed.

# Create a timestamped backup
sudo cp /opt/octostar/versions.yml /opt/octostar/versions.yml.backup.$(date +%Y%m%d_%H%M%S)

Pro Tip: Keep multiple backups for different rollback points. Consider archiving older backups to a separate location.

Step 2: Download Latest versions.yml

Download the latest version manifest for your chosen update track:

For Stable releases:

# Download stable versions.yml
sudo curl -o /opt/octostar/versions.yml https://install.octostar.com/versions/stable.yml

For Nightly releases:

# Download nightly versions.yml
sudo curl -o /opt/octostar/versions.yml https://install.octostar.com/versions/nightly.yml

Step 3: Execute Update

Run the update script to apply the new versions. The script performs a rolling update to minimize service disruption.

# Navigate to Octostar directory and run update
cd /opt/octostar && sudo bin/update-existing.sh
What happens during update:
  • 1Pull new container images from registry
  • 2Perform rolling restart with zero-downtime deployment
  • 3Run health checks on all services
  • 4Verify successful deployment

Step 4: Verify Installation

Confirm all services are running correctly after the update:

# Check service status
kubectl get pods -n octostar-main

# View current version
cat /opt/octostar/versions.yml | head -n 5

Quick Reference

For experienced users, here are single-command update sequences:

Update to Stable:

sudo cp /opt/octostar/versions.yml /opt/octostar/versions.yml.backup.$(date +%Y%m%d_%H%M%S) && \
sudo curl -o /opt/octostar/versions.yml https://install.octostar.com/versions/stable.yml && \
cd /opt/octostar && sudo bin/update-existing.sh

Update to Nightly:

sudo cp /opt/octostar/versions.yml /opt/octostar/versions.yml.backup.$(date +%Y%m%d_%H%M%S) && \
sudo curl -o /opt/octostar/versions.yml https://install.octostar.com/versions/nightly.yml && \
cd /opt/octostar && sudo bin/update-existing.sh

Troubleshooting & Rollback

Rollback to Previous Version

If you experience issues after updating, you can quickly rollback to your previous version:

# Restore your backup (replace timestamp with your backup)
sudo cp /opt/octostar/versions.yml.backup.20240101_120000 /opt/octostar/versions.yml

# Re-run update script to apply previous version
cd /opt/octostar && sudo bin/update-existing.sh

Common Issues

Download fails:

Check your internet connection and firewall rules. Ensure outbound HTTPS traffic is allowed to install.octostar.com

Pods not starting:

Run kubectl describe pod <pod-name> -n octostar-main to identify issues. Check image pull secrets and resource limits.

Update script errors:

Ensure you have sudo privileges and sufficient disk space. Check logs in /opt/octostar/logs/

Best Practices

  • Schedule Regular Updates: Plan updates during maintenance windows. Monthly for stable, weekly for nightly environments.
  • Test in Staging First: Always test updates in a staging environment before applying to production.
  • Review Release Notes: Check the changelog for breaking changes and new features before updating.
  • Monitor After Update: Keep an eye on system metrics and logs for at least 24 hours post-update.

Need Help?

If you encounter any issues during the update process, our support team is here to help:

  • Slack Community: Join our active community for peer support
  • Email Support: Reach out to support@octostar.com
  • Documentation: Browse our comprehensive guides and tutorials