Getting started

This document describes each stage of the Service Proxy for Kubernetes (SPK) integration process, and the command line interface (CLI) tools required to complete the integration. A careful review of this document ensures a positive experience.

_images/spk_info.png Note: You can click Next at the bottom of each page, or scroll through the SPK PDF to follow the integration process.

Integration tools

Install the CLI tools listed below on your Linux based workstation:

  • Helm CLI - Manages the SPK Pod and Custom Resource (CR) installations.
  • OpenSSL toolkit - Creates SSL certificates that secure Pod-to-Pod communication.
  • Podman - Tags and pushes software images to local registries.

Integration stages

Integrating the SPK software images involves five essential stages to begin processing application traffic, and two optional stages to enable logging collection and session-state data persistence:

  1. SPK Software - Extract and install the SPK software images and Custom Resource Definitions (CRDs).
  2. SPK Secrets - Secure communication between the SPK Controller and Service Proxy TMM Pods.
  3. Fluentd Logging - Optional: Centralize logging data sent from each of the installed SPK Pods.
  4. OTEL Collectors - Optional: Collect and view statistics from the SPK Controller and TMM Pods.
  5. dSSM Database - Optional: Store session-state data for the Service Proxy TMM Pod.
  6. SPK CWC - Install the Cluster Wide Controller to enable gathering SPK software telemetry.
  7. SPK Licensing - License the cluster to enable flexible consumption software use.
  8. SPK Controller - Prepare the cluster to proxy and load balance application traffic.
  9. SPK CRs - Configure a Custom Resource (CR) to begin processing application traffic.

Next step

Continue to the SPK Software guide to extract and install the SPK software.


Provide feedback to improve this document by emailing