- Include a webhook URL to send notifications after backups.
- Capture and log the duration and size of the backups.
- Create a new Kubernetes secret for storing the Feishu webhook URL.
- Enhance the backup script to notify users of backup success with details.
This change improves monitoring and user notification of backup events,
allowing for better awareness and response times in case of failure or
success of the backup processes.
- Create a new namespace for the backup system
- Implement a cron job for scheduled backups
- Add a daemon set to handle backup tasks across nodes
- Introduce necessary service accounts, roles, and role bindings
- Include environment variable handling and configuration via secrets and config maps
- Ensure triggering and execution workflow for backups is efficient
This commit establishes a new backup system that utilizes both a cron job and a daemon set to automate backups. It organizes the configurations and credentials needed for S3-compatible storage, allowing for seamless backup management across the specified nodes in the Kubernetes cluster.
- Create a cronjob to back up node1 data to node8
- Define schedule for daily backups at 3:00 AM
- Include error handling and notifications via Feishu
- Use SSH and rsync for secure and efficient data transfer
This commit introduces a new cronjob that automates the backup process
for node1 to node8, enabling easier management and recovery of data.
The setup includes necessary security measures and proper logging of backups,
ensuring smoother operation and notifications in case of failures.
- Remove specific hostname constraint from
nodeSelector for various components and add
region and datacenter keys.
This change allows more flexible scheduling of pods
across available nodes by removing the fixed
hostname requirement. It introduces the ability to
distribute workloads based on region and data center
while maintaining functional consistency across the
Kubernetes deployment.
- Changed storageClass from "local-vkus1" to "nfs-zgo-us1" for various components:
- api
- proxy
- ssrfProxy
- pluginDaemon
- postgresql
- redis
This update standardizes the storage class across multiple components,
potentially improving compatibility and performance with NFS-based storage.
It may help in better resource management and scalability.
- Change kind from Deployment to DaemonSet
- Remove previous node selector configuration
- Add tolerations for scheduling restrictions
- Introduce node affinity for specific hostnames
These changes facilitate deployment across all nodes instead of a single replica,
allowing for improved resource utilization and management in the
Kubernetes environment.
- Bump image version for `chatgpt-web-midjourney-proxy` from 2.22.7 to
2.23.8.
- Add annotations for NGINX ingress to configure proxy body size,
read timeout, and send timeout.
These changes enhance the deployment of the application by ensuring
that it uses the latest image version and improves the handling of
larger requests and longer processing time through appropriate NGINX
configuration.
- Enable hostPort for controller
- Disable external controller service
- Add new configuration options for Nginx controller with
allow-snippet-annotations and real-ip handling settings
These changes improve the networking configuration of the Nginx
Ingress controller, enabling better handling of forwarded IP
addresses and ensuring the correct annotations are applied.
It also modifies service accessibility to better fit internal
deployments.
- Change hostname from vkvm-us1 to zgocloud-us1
- Update persistent volume claim name from pg-data-local-vkus1-pvc to pg-data-local-zgus1-pvc
- Modify storage class name to local-zgus1
These updates ensure that the PostgreSQL deployment references the correct
Kubernetes node and persistent volume, aligning with the current
infrastructure and deployment strategy.
- Change storageClass values from 'local-vkus2' to 'local-zgus1'
- Update nodeSelector hostname from 'vkvm-us2' to 'zgocloud-us1'
- Modify persistent volume claim names to reflect new storage class
These changes aim to facilitate a smooth transition to a new hosting environment, ensuring that the resources are correctly allocated and managed.
- Introduce a new StorageClass named `local-data`
- Set provisioner to `rancher.io/local-path`
- Define parameters including `nodePath` and `pathPattern`
- Modify existing StorageClass from `local-data` to `local-zgus1` and include `nodeSelector`
This commit sets up a local storage class to be used within the Kubernetes environment, enabling better management of local volumes.
The new configuration allows for efficient volume binding based on specific node requirements.
- Include tolerations in load.yaml for scheduling
- Allow pods to tolerate specific constraints and improve scheduling
This change enables the containers to schedule on nodes with
restricted taints, enhancing deployment strategies in constrained
Kubernetes environments.
- Remove leading space in the OPENAI_API_MODEL value
- Ensure consistency in YAML formatting
This change corrects the spacing in the OPENAI_API_MODEL
configuration to maintain consistency in the YAML file, which helps
prevent potential issues during processing.
- Change model value from 'o1-mini-2024-09-12' to 'o3-mini'.
This update modifies the model used in the application configuration, which may lead to different behavior or performance improvements depending on the capabilities of the new model.
- Change value of OPENAI_API_MODEL from "o1-mini" to "o1-mini-2024-09-12"
This change updates the model version used in the configuration,
ensuring compatibility with the latest API requirements. The
previous model version will no longer receive updates or support, so
updating this configuration is necessary for continued functionality.
- Create deployment configuration for app3 with 5 replicas.
- Add service to expose app3 on port 3002.
- Define ingress resource for handling external traffic to app3.
- Set up TLS and host configuration for secure traffic.
This commit introduces the necessary Kubernetes manifests for the new
app3 which allows for deployment, service exposure, and ingress
routing, thereby enabling it to be accessed securely over the
specified domain. The deployment includes node affinity rules to
restrict execution environments and enhances the overall service
availability.
- Add tolerations for restricted scheduling
- Set externalTrafficPolicy to 'Local'
These updates enhance the deployment configuration of the nginx-ingress.
They allow better scheduling of pods on nodes with specific taints and
facilitate the preservation of the client source IP for external
traffic.
- Add clhk2.dev.todayaiweather.com to the list of hosts
- Add bwh1.dev.todayaiweather.com to the list of hosts
- Add spus1.dev.todayaiweather.com to the list of hosts
This update allows the application to handle traffic from four
subdomains, providing more flexibility for development and testing.
Each subdomain is routed to the same backend service, ensuring
a consistent experience across these endpoints.
- Modify ingress configuration to redirect requests for /Avatar.jpg
to a specific URL.
- Ensure that the redirection includes query parameters.
- Comment out the old rewrite rule for clarity.
This update addresses the routing for Avatar.jpg, ensuring that
requests are properly directed to the desired image location,
improving accessibility for users.
- Enable snippet annotations for nginx ingress controller
- Comment out a previous configuration snippet that redirects JPG files
This update allows the use of snippet annotations, giving more control
over ingress configurations. The previously commented snippet
suggested a redirect for JPG files but is now ignored to simplify
configuration and focus on the current requirements.
- Change retention period from 5 days to 3 days
This adjustment may help free up storage resources more
quickly, ensuring that older metrics are purged sooner,
leading to better performance and lower storage costs.
