This is the Experimental version (Latest). It is under active development and may change. For the most reliable documentation, use the version selector in the top-right to switch to Stable, or click here to go to the Stable version's homepage.

Opstella Kubernetes Integration Installation

อัพเดทล่าสุด: 13 มี.ค. 2569

เนื้อหานี้ยังไม่มีในภาษาของคุณ

🟢 Management

Opstella Kubernetes Integration (ok8s-integration) is a Service for Opstella to perform Licensing System and Usages Collection.

Application Dependencies

📦PostgreSQL-based Datastore ; Deploy external/dedicated instance of Database

Preparation

Kubernetes Cluster Preparation

Connect to 🟢 Management Kubernetes Cluster ; i.e w/ Kubeconfig File

Ensure you have defined and loaded your Global Shell Variables as described in Shell Variables.
Terminal window
```
source $BASE_WORKING_DIR/shell-values/kubernetes/management_cluster.vars.sh
```
Prepare 🟢 Management Kubernetes Cluster Information

Ensure K8S_INTERNAL_DOMAIN, K8S_INGRESSCLASS_NAME, K8S_STORAGECLASS_NAME are defined as per the Shell Variables guide.

Opstella Kubernetes Integration Datastore Preparation

Create PostgreSQL Initial Admin Credentials with Kubernetes Secret
- Username: postgres (Default Admin of PostgreSQL)
- Password: (Loaded from opstella-platform.vars.sh)

Provision PostgreSQL for Opstella Kubernetes Integration Datastore

The following manifest defines the entire PostgreSQL system using CloudNativePG, including credentials and the cluster.

cat <<EOF > $BASE_WORKING_DIR/kubernetes-manifests/ok8s-integration-postgres.yaml
---
# Postgres Superuser (root) Credentials
apiVersion: v1
kind: Secret
type: kubernetes.io/basic-auth
metadata:
  name: ok8s-integration-postgres-superuser
  namespace: opstella-system
stringData:
  username: postgres
  password: "${OPSTELLA_CORE_LICENSE_POSTGRES_SUPERUSER_PASSWORD}"
---
# ok8s-integration Application User Credentials
apiVersion: v1
kind: Secret
type: kubernetes.io/basic-auth
metadata:
  name: ok8s-integration-postgres-user
  namespace: opstella-system
stringData:
  username: ok8s_intergration_user
  password: "${OPSTELLA_CORE_LICENSE_POSTGRES_USER_PASSWORD}"
---
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: ok8s-integration-postgres
  namespace: opstella-system
  labels:
    app.kubernetes.io/name: ok8s-integration-postgres
    app.kubernetes.io/part-of: opstella-platform
spec:
  instances: 1

  # Image configuration (Postgres 15)
  imageName: ghcr.io/cloudnative-pg/postgresql:15

  # Storage Configuration
  storage:
    size: 2Gi
    storageClass: "${K8S_STORAGECLASS_NAME}"

  walStorage:
    size: 2Gi
    storageClass: "${K8S_STORAGECLASS_NAME}"

  # Bootstrap Configuration
  bootstrap:
    initdb:
      database: ok8s_intergration
      owner: ok8s_intergration_user
      # Secret containing password for the Application User
      secret:
        name: ok8s-integration-postgres-user

  # Superuser credentials (root/postgres)
  superuserSecret:
    name: ok8s-integration-postgres-superuser

  # Monitoring (disabled for now)
  monitoring:
    enablePodMonitor: false

  # Resources
  resources:
    requests:
      memory: "128Mi"
      cpu: "100m"
    limits:
      memory: "512Mi"
      cpu: "500m"

EOF

Apply the configuration:

kubectl apply -f $BASE_WORKING_DIR/kubernetes-manifests/ok8s-integration-postgres.yaml

💡 Should return secret/ok8s-integration-postgres-superuser, secret/ok8s-integration-postgres-user, and cluster.postgresql.cnpg.io/ok8s-integration-postgres created messages.

Opstella Kubernetes Integration Preparation

Prepare Helm Values Configurations.
- image.repository, image.tag : Set your Opstella Kubernetes Integration Container Image Location, Version
  - Online Installation
  - Air-gapped / Local Registry
  (Ensure OPSTELLA_REGISTRY is loaded from your variables)
  
  Ensure HARBOR_DOMAIN is defined as per the Shell Variables guide.
  
  (Ensure OPSTELLA_REGISTRY is loaded from your variables)
  (Ensure OPSTELLA_OK8S_VERSION is loaded from your variables)
- Datastore for Opstella Kubernetes Integration Information
  
  (Ensure datastore parameters are loaded from your vars file)
- Opstella Core Kubernetes Namespace
  
  (Ensure namespace is loaded from your vars file)

Create Helm Values Configuration.

cat <<EOF > $BASE_WORKING_DIR/helm-values/ok8s-integration-full-values.yaml
image:
  repository: ${OPSTELLA_CORE_LICENSE_IMAGE_REPOSITORY}
  tag: ${OPSTELLA_CORE_LICENSE_IMAGE_TAG}
  pullPolicy: Always

nameOverride: opstella-ok8s
fullnameOverride: opstella-ok8s

resources: {}

imagePullSecrets:
  - registry-secret

podAnnotations:
  dapr.io/enabled: "true"
  dapr.io/app-id: "core-license"
  dapr.io/app-port: "3000"
  dapr.io/enable-api-logging: "true"
  dapr.io/config: "config"
  dapr.io/sidecar-seccomp-profile-type: "RuntimeDefault"

containerPort: 3000

vars:
  INVOKE_URL: http://localhost:3500/v1.0/invoke/opstella-core.opstella-system.svc/method
  DB_HOST: "${OPSTELLA_CORE_LICENSE_POSTGRES_HOST}"
  DB_PORT: "${OPSTELLA_CORE_LICENSE_POSTGRES_PORT}"
  DB_NAME: "${OPSTELLA_CORE_LICENSE_POSTGRES_DB}"
  DB_USERNAME: "${OPSTELLA_CORE_LICENSE_POSTGRES_USER}"
  DB_PASSWORD: "${OPSTELLA_CORE_LICENSE_POSTGRES_USER_PASSWORD}"

## ReadinessProbe
probe:
  enabled: true
  path: "/"
  settings:
    initialDelaySeconds: 10
    periodSeconds: 60
    successThreshold: 1
    timeoutSeconds: 3
    failureThreshold: 3

# Before you use a liveness probe: https://srcco.de/posts/kubernetes-liveness-probes-are-dangerous.html
livenessProbe:
  enabled: true
  path: "/healthcheck"
  settings:
    initialDelaySeconds: 30
    periodSeconds: 60
    successThreshold: 1
    timeoutSeconds: 3
    failureThreshold: 3

volumes:
  - name: ok8s-integration-info
    existingSecret: ok8s-integration-info
    path: /app/config

podSecurityContext:
  fsGroup: 1000

securityContext:
  seccompProfile:
    type: RuntimeDefault
  capabilities:
    drop: ["ALL"]
  runAsNonRoot: true
  privileged: false
  allowPrivilegeEscalation: false
  runAsGroup: 1000
  runAsUser: 1000

EOF

Install Dapr Components CRDs

Create Cron Bindings

kubectl apply --namespace opstella-system -f - <<EOF
apiVersion: dapr.io/v1alpha1
kind: Component
spec:
  type: bindings.cron
  version: v1
  metadata:
    - name: schedule
      value: "5 * * * *"
    - name: route
      value: "/api/collect-data"
    - name: method
      value: POST
scopes:
  - core-license
metadata:
  name: cronjob-collect-data
EOF

Installation

Install Opstella Kubernetes Integration.

Install Helm Release using onechart Helm Chart with specific Helm Chart Version --version 0.73.0

helm upgrade --install ok8s-integration \
  oci://ghcr.io/gimlet-io/onechart --version 0.73.0 \
  --namespace opstella-system \
  -f $BASE_WORKING_DIR/helm-values/ok8s-integration-full-values.yaml

Post-Installation

Opstella Kubernetes Integration Testing

Get Pod Status - Opstella Kubernetes Integration and its Datastore Service
Terminal window
```
kubectl get pods -n opstella-system
```
- Opstella Kubernetes Integration should be Pending
- Its Datastore Service should be Running
Opstella Kubernetes Integration will stay in Pending status until the License is Activated.
```
NAME                                READY   STATUS    RESTARTS   AGE
... (deducted)
ok8s-integration-XXXXXXX-YYYYY      0/1     Pending   0          1m
ok8s-integration-postgres-1         1/1     Running   0          1m
```

Finished?

Use the below navigation to proceed

ก่อนหน้า
Opstella Workers ถัดไป
Installation