Sign inSign up

articomio/articom-k8s-crd

By articomio

•Updated 25 days ago

Official Helm Chart for Articom Kubernetes License Operator

Helm
0

721

articomio/articom-k8s-crd repository overview

⁠Articom Kubernetes Operator Helm Chart

Artifact Hub License Kubernetes

Official Helm Chart for deploying the Articom Kubernetes License Operator and its accompanying in-namespace HashiCorp Vault infrastructure.


⁠Overview

The Articom License Operator automates the deployment, scaling, credential distribution, and secret synchronization for the entire Articom AI & CX Microservices Suite based on validated license keys issued by admin.articom.io⁠.

⁠What This Chart Deploys:
  • Articom Controller Manager: Custom Kubernetes Operator reconciling License custom resources.
  • Custom Resource Definitions (CRDs): Includes the License (articom.inforwaves.com/v1alpha1) custom resource definition.
  • In-Namespace Vault (vaultarticom): Autonomous StatefulSet managing runtime secrets, tokens, and rolling updates.
  • RBAC & ServiceAccounts: Scoped permissions for controller and secret management.

⁠Quick Start Installation

⁠1. Install Chart from Docker Hub (OCI Registry)
# Install the latest release into the 'articom-system' namespace
helm install articom-operator oci://registry-1.docker.io/articomio/articom-k8s-crd \
  --namespace articom-system \
  --create-namespace
⁠2. Apply Your License Key

Create a license.yaml file with your Articom license key:

apiVersion: articom.inforwaves.com/v1alpha1
kind: License
metadata:
  name: articom-license
  namespace: articom-system
spec:
  # Replace with your license key from https://admin.articom.io
  key: "YOUR_ARTICOM_LICENSE_KEY"

Apply it to the cluster:

kubectl apply -f license.yaml
⁠3. Verify Deployment & Status
# Check the License status
kubectl get license -n articom-system

# Check running pods (Operator, Vault, and provisioned services)
kubectl get pods -n articom-system

⁠Configuration (values.yaml)

You can override default parameters during installation using --set key=value or by supplying a custom values.yaml file (-f my-values.yaml).

ParameterDefaultDescription
manager.image.repositoryarticomio/articom-cx-operatorOperator controller manager container image repository
manager.image.taglatestOperator image tag
manager.image.pullPolicyIfNotPresentImage pull policy for operator manager
manager.replicas1Number of operator manager replicas
vault.enabletrueEnables deployment of the in-namespace HashiCorp Vault instance
vault.rootToken""Predefined root token for Vault (auto-generated if empty)
vault.storage.size10GiPersistent Volume Claim size for Vault backend storage
vault.storage.storageClass""StorageClass for Vault PVC ("" uses cluster default)
crd.enabletrueAutomatically installs and manages CRDs with this chart

⁠Managed Services & Endpoints

Once the License resource is applied, the operator automatically provisions and manages authorized microservices as internal ClusterIP services on Port 80:

ServiceProtocolInternal PortDescription
articom-api-serviceHTTP/REST80Core GraphQL & REST API backend
articom-ai-serviceHTTP80AI & LLM conversational engine
articom-knowledge-serviceHTTP80Vector search & knowledge base
articom-chat-widget-serviceHTTP80Customer chat widget web application
articom-consumer-portal-serviceHTTP80Customer self-service portal
articom-kyc-serviceHTTP80Identity verification & KYC service
articom-saas-serviceHTTP80SaaS management dashboard

⁠Upgrading & Uninstallation

⁠Upgrade Release:
helm upgrade articom-operator oci://registry-1.docker.io/articomio/articom-k8s-crd \
  --namespace articom-system
⁠Uninstall Release:
helm uninstall articom-operator --namespace articom-system

⁠Support & Enterprise Licensing

Tag summary

Content type

Helm

Digest

sha256:16ffdffae…

Size

9.8 kB

Last updated

25 days ago

helm pull oci://registry-1.docker.io/articomio/articom-k8s-crd --version latest