Fishjam JS Server SDK
software-mansion-labs/skills
Node.js / TypeScript server SDK for Fishjam — backends that create rooms, mint peer tokens, listen to server notifications, and run agents.
A skill your agent uses to implement TLS security profiles for operators and workloads on OpenShift.
$ npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers openshift-tls-profile --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/openshift-tls-profile/skills/openshift-tls-profile .claude/skills/openshift-tls-profile && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openshift-tls-profile" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profile into .claude/skills/openshift-tls-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openshift-tls-profile", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profileType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers openshift-tls-profile --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/openshift-tls-profile/skills/openshift-tls-profile .agents/skills/openshift-tls-profile && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openshift-tls-profile" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profile into .agents/skills/openshift-tls-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openshift-tls-profile", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers openshift-tls-profile --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/openshift-tls-profile/skills/openshift-tls-profile .cursor/skills/openshift-tls-profile && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openshift-tls-profile" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profile into .cursor/skills/openshift-tls-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openshift-tls-profile", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/openshift-tls-profile/skills/openshift-tls-profile--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers openshift-tls-profile --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/openshift-tls-profile/skills/openshift-tls-profile .gemini/skills/openshift-tls-profile && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openshift-tls-profile" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profile into .gemini/skills/openshift-tls-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openshift-tls-profile", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-eng/ai-helpers openshift-tls-profileInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/openshift-tls-profile/skills/openshift-tls-profile .github/skills/openshift-tls-profile && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openshift-tls-profile" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profile into .github/skills/openshift-tls-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openshift-tls-profile", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers openshift-tls-profile --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/openshift-tls-profile/skills/openshift-tls-profile .opencode/skills/openshift-tls-profile && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openshift-tls-profile" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-tls-profile/skills/openshift-tls-profile into .opencode/skills/openshift-tls-profile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openshift-tls-profile", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
openshift-tls-profileA skill your agent uses to implement TLS security profiles for operators and workloads on OpenShift.
Openshift Tls Profile is an agent skill from openshift-eng/ai-helpers. Use this skill to implement TLS security profiles for operators and workloads on OpenShift. Provides guidance on reading TLS config from APIServer CR and applying it to webhook/metrics servers, HTTP, and gRPC endpoints.
Its SKILL.md is about 6.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Cryptography, gRPC and Protobuf and Webhooks. It works with gRPC. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
jqFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.compkg.go.devwiki.mozilla.orgdocs.redhat.comdocs.openshift.comaccess.redhat.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Openshift Tls Profile loads about 6.1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,624 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 1,624 words, ~6,100 tokens.
.claude/skills/openshift-tls-profile/SKILL.md (or your agent's skills folder).This skill helps implement TLS security profiles for operators and workloads running on OpenShift. It provides complete guidance on reading TLS configuration from OpenShift cluster and applying it consistently across all secured endpoints.
This skill implements the requirements defined in the Centralized and Enforced TLS Configuration Enhancement. The enhancement addresses the gap where many OpenShift components hardcode TLS settings or rely on library defaults rather than respecting cluster-wide TLS configuration. Key points:
The API changes are implemented in openshift/api#2680, which adds the TLSAdherence feature gate and tlsAdherence field to apiserver.config.openshift.io/v1.
The tlsAdherence field in the APIServer CR controls how strictly components adhere to the configured TLS security profile:
| Mode | Description |
|---|---|
| Legacy (default) | Backward-compatible behavior. Components attempt to honor the configured TLS profile but may fall back to their individual defaults if conflicts arise. Intended for clusters that need to maintain compatibility during migration. |
| Strict | Enforces strict adherence to the TLS configuration. All components must honor the configured profile without fallbacks. Recommended for security-conscious deployments and required for certain compliance frameworks. |
Feature Gate: The TLSAdherence feature gate controls this functionality. It is currently enabled in DevPreviewNoUpgrade and TechPreviewNoUpgrade.
Implementation Note: When implementing TLS profile support in your operator, ensure your component applies the configured TLS profile and reports degraded status on failure in both modes. In Strict mode, components that fail to apply the configured TLS profile should report degraded status rather than silently falling back to defaults.
Default Source: API Server Configuration
Most components should use the API Server configuration as their TLS profile source. This is the default and preferred option. If you're unsure which source to use, start with the API Server configuration.
Order of Precedence (use only if you have a specific reason to deviate from API Server):
| Source | When to Use |
|---|---|
| API Server (default) | Use this by default. Most OpenShift operators use library-go's apiserver config observer pattern, which automatically observes the API Server TLS profile. |
| Kubelet | Only use if your component is specifically running on the kubelet and needs to match kubelet's TLS settings. |
| Ingress Controller | Only use if your component is specifically handling ingress traffic and needs to match the ingress controller's TLS settings. |
Use this skill when:
crypto/tls configurationOperators implementing TLS security profiles must satisfy these requirements:
apiservers.config.openshift.io/clusterThere are several approaches to respond to TLS profile changes:
Option A: Use controller-runtime-common Package (Recommended for controller-runtime)
For operators using controller-runtime, the recommended approach is to use the official package:
github.com/openshift/controller-runtime-common/pkg/tlsThis package provides all necessary utilities for TLS profile implementation.
Quick Start Example:
package main
import (
"context"
"crypto/tls"
"os"
configv1 "github.com/openshift/api/config/v1"
openshifttls "github.com/openshift/controller-runtime-common/pkg/tls"
"sigs.k8s.io/controller-runtime/pkg/metrics/filters"
"k8s.io/apimachinery/pkg/runtime"
utilruntime "k8s.io/apimachinery/pkg/util/runtime"
clientgoscheme "k8s.io/client-go/kubernetes/scheme"
ctrl "sigs.k8s.io/controller-runtime"
"sigs.k8s.io/controller-runtime/pkg/client"
metricsserver "sigs.k8s.io/controller-runtime/pkg/metrics/server"
"sigs.k8s.io/controller-runtime/pkg/webhook"
)
var scheme = runtime.NewScheme()
func init() {
utilruntime.Must(clientgoscheme.AddToScheme(scheme))
utilruntime.Must(configv1.AddToScheme(scheme))
}
func main() {
// Create a cancellable context for graceful shutdown on TLS profile changes
ctx, cancel := context.WithCancel(ctrl.SetupSignalHandler())
defer cancel()
cfg := ctrl.GetConfigOrDie()
// Create a temporary client to fetch initial TLS profile
tempClient, err := client.New(cfg, client.Options{Scheme: scheme})
if err != nil {
os.Exit(1)
}
// Fetch the TLS profile from APIServer CR
tlsProfileSpec, err := openshifttls.FetchAPIServerTLSProfile(ctx, tempClient)
if err != nil {
os.Exit(1)
}
// Convert to TLSOpts function for controller-runtime
tlsOpts, unsupportedCiphers := openshifttls.NewTLSConfigFromProfile(tlsProfileSpec)
if len(unsupportedCiphers) > 0 {
// Log warning about unsupported ciphers
}
mgr, err := ctrl.NewManager(cfg, ctrl.Options{
Scheme: scheme,
Metrics: metricsserver.Options{
BindAddress: ":8443",
SecureServing: true,
FilterProvider: filters.WithAuthenticationAndAuthorization,
TLSOpts: []func(*tls.Config){tlsOpts},
},
WebhookServer: webhook.NewServer(webhook.Options{
Port: 9443,
TLSOpts: []func(*tls.Config){tlsOpts},
}),
})
if err != nil {
os.Exit(1)
}
// Set up the TLS profile watcher to trigger graceful shutdown on changes
watcher := &openshifttls.SecurityProfileWatcher{
Client: mgr.GetClient(),
InitialTLSProfileSpec: tlsProfileSpec,
OnProfileChange: func(ctx context.Context, old, new configv1.TLSProfileSpec) {
// Cancel context to trigger graceful shutdown and reload
cancel()
},
}
if err := watcher.SetupWithManager(mgr); err != nil {
os.Exit(1)
}
if err := mgr.Start(ctx); err != nil {
os.Exit(1)
}
}Package Functions:
| Function | Purpose |
|---|---|
FetchAPIServerTLSProfile(ctx, client) | Fetches TLS profile spec from APIServer CR, returns default (Intermediate) if not set |
GetTLSProfileSpec(profile) | Resolves profile type (Old/Intermediate/Modern/Custom) to TLSProfileSpec |
NewTLSConfigFromProfile(spec) | Returns a func(*tls.Config) for controller-runtime's TLSOpts + list of unsupported ciphers |
SecurityProfileWatcher | Controller that watches APIServer and triggers callback on TLS profile changes |
SecurityProfileWatcher:
The SecurityProfileWatcher is a controller that watches the APIServer CR and invokes a callback when the TLS profile changes:
watcher := &openshifttls.SecurityProfileWatcher{
Client: mgr.GetClient(),
InitialTLSProfileSpec: initialProfile,
OnProfileChange: func(ctx context.Context, old, new configv1.TLSProfileSpec) {
// Common pattern: cancel context to trigger graceful shutdown
// The operator will restart and pick up the new TLS configuration
cancel()
},
}
if err := watcher.SetupWithManager(mgr); err != nil {
return err
}Note: The watcher handles predicates internally - it only watches the "cluster" APIServer object and compares profile changes using reflect.DeepEqual.
Restart vs Hot-Reload Trade-offs:
| Approach | Restart Required | Existing Connections | Recommendation |
|---|---|---|---|
| SecurityProfileWatcher | Yes - graceful shutdown | All connections use new TLS settings after restart | Recommended - ensures consistent TLS policy across all connections |
| GetConfigForClient (Option D) | No | Not updated - only new connections use new settings | Use only when restarts are not acceptable |
Why SecurityProfileWatcher is recommended:
GetConfigForClient leaves existing long-lived connections using the old TLS configurationOption B: For OpenShift Operators (configobserver pattern)
This is the recommended approach for OpenShift operators using the library-go configobserver pattern. Use library-go's ObserveTLSSecurityProfile function from the apiserver config observer package. This function:
APIServerLister().Get("cluster")) - this is the default source for all componentscrypto.OpenSSLToIANACipherSuitesservingInfo.minTLSVersion and servingInfo.cipherSuites in the observed configmap[string]interface{} in the format expected by your operator's observed configpackage configobserver
import (
"github.com/openshift/library-go/pkg/operator/configobserver"
"github.com/openshift/library-go/pkg/operator/configobserver/apiserver"
"github.com/openshift/library-go/pkg/operator/events"
)
// In your config observer controller's ObserveConfig method
func (c *MyConfigObserver) ObserveConfig(
listers configobserver.Listers,
recorder events.Recorder,
existingConfig map[string]interface{},
) (map[string]interface{}, []error) {
// ObserveTLSSecurityProfile observes APIServer.Spec.TLSSecurityProfile and sets
// servingInfo.minTLSVersion and servingInfo.cipherSuites in observedConfig
observedConfig, errs := apiserver.ObserveTLSSecurityProfile(listers, recorder, existingConfig)
// ... merge with other observed config
return observedConfig, errs
}Option C: Watch from Existing Controller
If your operator cannot use the SecurityProfileWatcher (Option A) or the configobserver pattern (Option B), use this approach. Watch the APIServer resource from your existing controller to trigger operand reconciliation when the TLS profile changes, allowing you to update operand deployments with the new TLS settings:
package controller
import (
"context"
"reflect"
configv1 "github.com/openshift/api/config/v1"
"k8s.io/apimachinery/pkg/runtime"
"k8s.io/apimachinery/pkg/types"
ctrl "sigs.k8s.io/controller-runtime"
"sigs.k8s.io/controller-runtime/pkg/builder"
"sigs.k8s.io/controller-runtime/pkg/client"
"sigs.k8s.io/controller-runtime/pkg/event"
"sigs.k8s.io/controller-runtime/pkg/handler"
"sigs.k8s.io/controller-runtime/pkg/predicate"
"sigs.k8s.io/controller-runtime/pkg/reconcile"
myv1 "myoperator/api/v1"
)
type MyOperandReconciler struct {
client.Client
Scheme *runtime.Scheme
}
func (r *MyOperandReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl.Result, error) {
// Fetch operand
operand := &myv1.MyOperand{}
if err := r.Get(ctx, req.NamespacedName, operand); err != nil {
return ctrl.Result{}, client.IgnoreNotFound(err)
}
// Fetch current TLS profile
profile, err := GetTLSSecurityProfile(ctx, r.Client)
if err != nil {
return ctrl.Result{}, err
}
// Apply TLS configuration to operand's deployment/pods
// This could involve updating a ConfigMap, Secret, or Deployment annotation
// to trigger a rolling restart of operand pods with new TLS settings
if err := r.reconcileOperandTLS(ctx, operand, profile); err != nil {
return ctrl.Result{}, err
}
return ctrl.Result{}, nil
}
func (r *MyOperandReconciler) SetupWithManager(mgr ctrl.Manager) error {
return ctrl.NewControllerManagedBy(mgr).
For(&myv1.MyOperand{}).
// Watch APIServer and trigger reconcile for all operands when TLS profile changes
Watches(
&configv1.APIServer{},
handler.EnqueueRequestsFromMapFunc(r.mapAPIServerToOperands),
builder.WithPredicates(tlsProfileChangedPredicate()),
).
Complete(r)
}
// mapAPIServerToOperands returns reconcile requests for all operands when APIServer changes
func (r *MyOperandReconciler) mapAPIServerToOperands(ctx context.Context, obj client.Object) []reconcile.Request {
// Only react to the "cluster" APIServer
if obj.GetName() != "cluster" {
return nil
}
// List all operands and trigger reconcile for each
var operands myv1.MyOperandList
if err := r.List(ctx, &operands); err != nil {
return nil
}
requests := make([]reconcile.Request, len(operands.Items))
for i, op := range operands.Items {
requests[i] = reconcile.Request{
NamespacedName: types.NamespacedName{
Name: op.Name,
Namespace: op.Namespace,
},
}
}
return requests
}
// tlsProfileChangedPredicate filters events to only TLS profile changes
func tlsProfileChangedPredicate() predicate.Predicate {
return predicate.Funcs{
CreateFunc: func(e event.CreateEvent) bool {
return e.Object.GetName() == "cluster"
},
UpdateFunc: func(e event.UpdateEvent) bool {
if e.ObjectNew.GetName() != "cluster" {
return false
}
oldAPI, ok := e.ObjectOld.(*configv1.APIServer)
if !ok {
return false
}
newAPI, ok := e.ObjectNew.(*configv1.APIServer)
if !ok {
return false
}
// Only reconcile if TLS profile actually changed
return !reflect.DeepEqual(
oldAPI.Spec.TLSSecurityProfile,
newAPI.Spec.TLSSecurityProfile,
)
},
DeleteFunc: func(e event.DeleteEvent) bool {
return false
},
GenericFunc: func(e event.GenericEvent) bool {
return false
},
}
}
func (r *MyOperandReconciler) reconcileOperandTLS(
ctx context.Context,
operand *myv1.MyOperand,
profile *configv1.TLSSecurityProfile,
) error {
// Update operand deployment with new TLS settings
// For example, update an annotation to trigger rolling restart:
//
// deployment.Spec.Template.Annotations["tls-profile-hash"] = hashTLSProfile(profile)
//
// Or update a ConfigMap/Secret that the operand mounts
return nil
}This approach is efficient because:
Option D: Dynamic TLS Config Update (Not Recommended)
An alternative approach uses Go's GetConfigForClient callback to dynamically return TLS configuration for each new connection without requiring a restart. However, this approach is not recommended because:
For consistent TLS policy enforcement, use Option A (SecurityProfileWatcher with graceful restart) or Option C (watch and reconcile) instead.
Use FetchAPIServerTLSProfile from the controller-runtime-common package to retrieve the TLS security profile:
import (
openshifttls "github.com/openshift/controller-runtime-common/pkg/tls"
)
// Fetch the TLS profile from APIServer CR
// Returns default Intermediate profile if not set
tlsProfileSpec, err := openshifttls.FetchAPIServerTLSProfile(ctx, client)
if err != nil {
return err
}This function fetches the TLSSecurityProfile from apiservers.config.openshift.io/cluster and returns the default Intermediate profile if none is configured.
Use NewTLSConfigFromProfile from the controller-runtime-common package to convert the TLS profile spec to a func(*tls.Config) suitable for controller-runtime:
import (
openshifttls "github.com/openshift/controller-runtime-common/pkg/tls"
)
// Convert to TLSOpts function for controller-runtime
// Returns a func(*tls.Config) that sets MinVersion and CipherSuites
tlsOpts, unsupportedCiphers := openshifttls.NewTLSConfigFromProfile(tlsProfileSpec)
if len(unsupportedCiphers) > 0 {
// Log warning about unsupported ciphers (ciphers not available in Go's crypto/tls)
log.Info("Some ciphers from TLS profile are not supported", "ciphers", unsupportedCiphers)
}This function handles:
crypto/tls constantsFor controller-runtime webhook and metrics servers, see the complete Quick Start Example in Option A above.
For other endpoints:
All TLS-enabled endpoints in your operator and operand must honor the cluster TLS configuration. This includes:
| Endpoint Type | How to Apply TLS Config |
|---|---|
| HTTP Client | Set Transport.TLSClientConfig on http.Client |
| HTTP Server | Set TLSConfig on http.Server |
| gRPC Client | Use grpc.WithTransportCredentials(credentials.NewTLS(tlsConfig)) with grpc.NewClient() |
| gRPC Server | Use grpc.Creds(credentials.NewTLS(tlsConfig)) with grpc.NewServer() |
For each endpoint, use the *tls.Config returned by TLSConfigFromProfile() (Step 2) to configure:
MinVersion - minimum TLS protocol versionCipherSuites - allowed cipher suites (only applies to TLS 1.2 and below)Key principle: No HTTP or gRPC endpoint should use hardcoded TLS settings. Always derive TLS configuration from the cluster's APIServer CR to ensure consistent security policy enforcement across all components.
OpenShift supports four TLS profile types based on Mozilla's Server Side TLS recommendations:
| Profile | Min TLS Version | Description |
|---|---|---|
| Old | TLS 1.0 | Legacy compatibility, not recommended for production |
| Intermediate (default) | TLS 1.2 | Recommended for general use, balances security and compatibility |
| Modern | TLS 1.3 | Highest security, may not work with older clients |
| Custom | Configurable | User-defined ciphers and minimum TLS version |
Default Profile: When spec.tlsSecurityProfile is not set in the APIServer CR, the Intermediate profile is used as the default. This provides a good balance between security and compatibility.
Note: In Go, cipher suites are not configurable for TLS 1.3 - they are automatically selected by the runtime.
The TLS profile is configured in the APIServer custom resource named cluster. If spec.tlsSecurityProfile is not specified, the Intermediate profile is used by default.
apiVersion: config.openshift.io/v1
kind: APIServer
metadata:
name: cluster
spec:
audit:
profile: Default
# tlsSecurityProfile is optional. If not set, defaults to Intermediate profile.
tlsSecurityProfile:
# type can be: Old, Intermediate, Modern, or Custom
type: Intermediate
# Only one of the following should be set based on type:
old: {}
intermediate: {}
modern: {}
custom:
ciphers:
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
minTLSVersion: VersionTLS12Reference:
Check the current TLS security profile in your cluster:
# Get the full APIServer configuration
oc get apiserver cluster -o yaml
# Get just the TLS security profile (empty output means default Intermediate profile is used)
oc get apiserver cluster -o jsonpath='{.spec.tlsSecurityProfile}' | jq .
# Check the effective TLS profile type (empty means Intermediate default)
oc get apiserver cluster -o jsonpath='{.spec.tlsSecurityProfile.type}'Note: If the above commands return empty output, the cluster is using the default Intermediate profile.
Note: For controller-runtime users, NewTLSConfigFromProfile from github.com/openshift/controller-runtime-common/pkg/tls handles all cipher conversion automatically. The utilities below are primarily for:
The github.com/openshift/library-go/pkg/crypto package provides utilities for converting between OpenShift TLS profile configurations and Go's crypto/tls types:
| Function | Purpose |
|---|---|
TLSVersion(name string) (uint16, error) | Convert TLS version name (e.g., "VersionTLS12") to Go constant |
CipherSuitesOrDie(names []string) []uint16 | Convert IANA cipher names to Go constants |
OpenSSLToIANACipherSuites(ciphers []string) []string | Map OpenSSL cipher names to IANA names |
SecureTLSConfig(config *tls.Config) *tls.Config | Apply secure defaults to a TLS config |
DefaultCiphers() []uint16 | Get default cipher suites for Intermediate profile |
Why these exist: OpenShift's configv1.TLSProfiles uses OpenSSL-format cipher names, not Go constants. These utilities handle the conversion.
© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/openshift-tls-profile/skills/openshift-tls-profile of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Openshift Tls Profile next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openshift Tls Profile this skillopenshift-eng/ai-helpers | 120 | — | ~6.1k | Automated safety check: Pass | Apache-2.0 | |
| Fishjam JS Server SDKsoftware-mansion-labs/skills | 291 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Quicknode Skillinternet-court/internet-court-skill | 6.4k | — | ~11k | Automated safety check: Pass | MIT | |
| Quicknodesendaifun/skills | 130 | 1 repos | ~5.5k | Automated safety check: Notes | Apache-2.0 | |
| API ForgeEliasOulkadi/shokunin | 114 | — | ~2.9k | Automated safety check: Pass | MIT | |
| API Designtravisjneuman/.claude | 101 | 1 repos | ~2.5k | Automated safety check: Pass | MIT |
software-mansion-labs/skills
Node.js / TypeScript server SDK for Fishjam — backends that create rooms, mint peer tokens, listen to server notifications, and run agents.
internet-court/internet-court-skill
Quicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap…
sendaifun/skills
Quicknode blockchain infrastructure for Solana — RPC endpoints, DAS API (Digital Asset Standard) for NFTs and compressed assets, Yellowstone gRPC streaming, Priority Fee API, Streams (real-time data…
EliasOulkadi/shokunin
Design REST/GraphQL APIs with OpenAPI 3.1, error handling, pagination, rate limiting, webhooks, and idempotency.
travisjneuman/.claude
REST and GraphQL API design best practices including OpenAPI specs.
majiayu000/claude-skill-registry
Comprehensive guide for Helius - Solana's leading RPC and API infrastructure provider.
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
openshift-eng/ai-helpers
Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
openshift-eng/ai-helpers
Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file
Works with
Categories
A skill your agent uses to implement TLS security profiles for operators and workloads on OpenShift. Openshift Tls Profile is an agent skill from openshift-eng/ai-helpers. Use this skill to implement TLS security profiles for operators and workloads on OpenShift.
Openshift Tls Profile fits situations like: implement TLS security profiles for operators and workloads on OpenShift; tasks that involve Cryptography; tasks that involve gRPC and Protobuf.
Run `npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a claude-code`. Or copy the skill folder (plugins/openshift-tls-profile/skills/openshift-tls-profile in openshift-eng/ai-helpers) into .claude/skills/openshift-tls-profile in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a codex`. Or copy the skill folder (plugins/openshift-tls-profile/skills/openshift-tls-profile in openshift-eng/ai-helpers) into .agents/skills/openshift-tls-profile in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill openshift-tls-profile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openshift-tls-profile, .gemini/skills/openshift-tls-profile, .github/skills/openshift-tls-profile and .opencode/skills/openshift-tls-profile in your project.
Going by SKILL.md and its folder, Openshift Tls Profile needs the command-line tools its instructions call (jq).
SKILL.md names 6 domains. As links in the text: github.com, pkg.go.dev, wiki.mozilla.org, docs.redhat.com, docs.openshift.com and access.redhat.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Openshift Tls Profile is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.1k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Openshift Tls Profile: Fishjam JS Server SDK (software-mansion-labs/skills, 291 stars), Quicknode Skill (internet-court/internet-court-skill, 6.4k stars), Quicknode (sendaifun/skills, 130 stars) and API Forge (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.
Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.