NOISSUE - Add medium blog for prism DevOps#48
Open
smithjilks wants to merge 5 commits into
Open
Conversation
JeffMboya
approved these changes
Feb 23, 2026
Signed-off-by: Jilks Smith <smithjilks@gmail.com>
Signed-off-by: Jilks Smith <smithjilks@gmail.com>
smithjilks
force-pushed
the
NOISSUE-prism-devops
branch
from
886fdbf to
63a5030
Compare
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
uvc-website | 31e5f0b | Commit Preview URL Branch Preview URL |
May 04 2026, 08:44 AM |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a new long-form blog post about Prism AI’s DevOps and Kubernetes architecture to the website’s Astro content collection. It extends the existing product/architecture blog catalog with a documentation-focused article that covers infrastructure, GitOps, observability, security, and CI/CD practices.
Changes:
- Adds a new blog post at
src/content/blog/prism-ai-kubernetes-architecture.md. - Introduces frontmatter metadata, cover/OG image references, and embedded architecture diagrams/snippets for the post.
- Documents Prism AI’s platform architecture across Kubernetes orchestration, networking, security, backups, and delivery workflows.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - SpiceDB for fine-grained authorization | ||
| - PostgreSQL for persistence | ||
| - Redis for caching | ||
| - Nats for event streaming |
| - PostgreSQL for persistence | ||
| - Redis for caching | ||
| - Nats for event streaming | ||
| - Opensearch for log analytics |
Comment on lines
+90
to
+94
| - **Staging Strategy**: Uses a simplified rolling update strategy to ensure rapid iteration loops. ArgoCD synchronizes these definitions from Git, ensuring that the cluster always matches the declarative state. | ||
|
|
||
| ### Automated Image Updates | ||
|
|
||
| ArgoCD Image Updater is used to automatically monitor container registries and update the deployments when new images are available: |
Comment on lines
+90
to
+94
| - **Staging Strategy**: Uses a simplified rolling update strategy to ensure rapid iteration loops. ArgoCD synchronizes these definitions from Git, ensuring that the cluster always matches the declarative state. | ||
|
|
||
| ### Automated Image Updates | ||
|
|
||
| ArgoCD Image Updater is used to automatically monitor container registries and update the deployments when new images are available: |
|
|
||
| ### Backup with Velero | ||
|
|
||
| In order to ensure resilience and availability of user data whenever an incident occurs, Prism AI uses Velero for disaster recovery. Backups are done regularly. You can have a look at [https://velero.io/](https://velero.io/) for more information on configuring back ups. |
| 1. Code commit triggers GitHub Actions | ||
| 2. Docker images built and tested | ||
| 3. Helm repository is updated with new image references | ||
| 4. ArgoCD detects changes and syncs to cluster |
|
|
||
| ## Conclusion | ||
|
|
||
| There are a lot of lessons that can be drawn from the Prism AI architecture, CI/CD, and DevOps practices, especially when it comes to cost optimisation without compromising on excellence and security. The platform makes good use of open-source production-ready tools. They also utilize Digital Ocean primarily, which is a lot cheaper than other Cloud Providers. Let's look at some of the considerations below: |
| - Redis for caching | ||
| - Nats for event streaming | ||
| - Opensearch for log analytics | ||
| - Fluentbit for log collection |
ianmuchyri
requested changes
May 4, 2026
| name: "Jilks Smith" | ||
| picture: "https://avatars.githubusercontent.com/u/41241359?v=4" | ||
| tags: ["prism ai", "kubernetes", "gitops", "devops", "cloud-native", "argocd", "devsecops"] | ||
| date: 2026-02-17 |
| - **Cost Optimization**: Advanced resource scheduling and spot instance usage | ||
| - **Multi-Cloud Deployment**: Cross-cloud redundancy and disaster recovery | ||
| - **Kubernetes Operators**: Custom operators for application lifecycle management | ||
| - **Advanced Scheduling**: Topology-aware scheduling and resource optimization |
Contributor
There was a problem hiding this comment.
Add links to Prism AI website and docs if someone wants to learn more
Signed-off-by: Jilks Smith <smithjilks@gmail.com>
Signed-off-by: Jilks Smith <smithjilks@gmail.com>
SammyOina
requested changes
May 4, 2026
Contributor
SammyOina
left a comment
SammyOina
left a comment
There was a problem hiding this comment.
The tone perhaps should be how we ensure prism availability at all times to enable customers know we are always up rather than technical depth
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This is a documentation because it adds blog for PRISM's DevOps
What does this do?
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Did you document any new/modified features?
Notes
To be merged after migration PR #42