The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
When you deploy Graph Studio using operator, following are the set of images used for actual deployments. We have given reference docker commands to download the latest releases for each of them below.
For deploying Graph Studio operator and CRs managed by it, user needs to enable RBAC and configure kubernetes objects mentioned below.
NOTE: One needs to edit operator deployment, CR deployment with right docker image details.
The following table lists the configurable parameters for Graph Studio and their default values.(CR API Version: v2)
Parameter | Description | Default |
---|---|---|
metadata.name | Name of CR | |
metadata.namespace | Namespace of CR | |
metadata.labels | Dictionary of (key: val) as labels of CR | |
spec.nodeConfig.spec | Configuration specification for Graph Studio | |
spec.nodeConfig.spec.replicas | Number of pods for Graph Studio Agent or Server | 1 |
spec.nodeConfig.spec.serviceName | Name of headless service for Graph Studio | anzo-<metadata.name> |
spec.nodeConfig.spec.template.spec.serviceAccountName | Service account name for pods | anzo-operator |
spec.nodeConfig.spec.template.spec.containers.x.Name | Name of Graph Studio container | anzo |
spec.service | Graph Studio loadbalancer service attributes, of type v1.Service | commented, please uncomment to add value |
spec.volumes | List of persistent volumes for Graph Studio | commented, please uncomment to add value |
spec.volumes.[i].name | Name for persistent volume | |
spec.volumes.[i].mountPath | Path where persistent volume should be mounted inside container | |
spec.volumes.[i].pv | Attributes to configure persistent volume, of type v1.PersistentVolume | |
spec.volumes.[i].pvc | Attributes to configure persistent volume claim, of type v1.PersistentVolumeClaim | |
spec.volumes.[i].deletePVC | Set this to true if you want to delete PVC after CR deletion | false |
spec.role | Role of Graph Studio, AnzoAgent or AnzoServer | |
spec.credentials | Existing credentials for AnzoAgent or AnzoServer | commented, please uncomment to add value |
spec.jsonActivation | Set this to true if Graph Studio should be activated using JSON data file | |
spec.bootProperties | Dictinary having <filename: filecontent> combination to configure boot properties at Graph Studio installation | |
spec.jvmMemory | Amount of memory that should be given for JVM processing | (Pod Memory - 1204M) | |
spec.licensing | User provided licensing information | commented, please uncomment to add value |
spec.licensing.licenseType | license type to use, AltairOne or CSI | commented, please uncomment to add value |
spec.licensing.altairOne | AltairOne licensing information | commented, please uncomment to add value |
spec.licensing.altairOne.authCode | AltairOne authentication code | commented, please uncomment to add value |
spec.licensing.altairOne.credentials | AltairOne credentials | commented, please uncomment to add value |
spec.licensing.altairOne.credentials.username | AltairOne username | commented, please uncomment to add value |
spec.licensing.altairOne.credentials.password | AltairOne password | commented, please uncomment to add value |
spec.licensing.altairOne.licenseFile | AltairOne license file | commented, please uncomment to add value |
spec.licensing.altairOne.licenseServer | AltairOne internal license server | commented, please uncomment to add value |
spec.licensing.altairOne.proxy | AltairOne proxy server | commented, please uncomment to add value |
spec.licensing.altairOne.proxy.credentials | AltairOne license proxy credentials | commented, please uncomment to add value |
spec.licensing.altairOne.proxy.credentials.username | AltairOne license proxy credentials username | commented, please uncomment to add value |
spec.licensing.altairOne.proxy.credentials.password | AltairOne license proxy credentials password | commented, please uncomment to add value |
spec.licensing.altairOne.proxy.credentials.host | AltairOne proxy server host | commented, please uncomment to add value |
spec.licensing.altairOne.proxy.credentials.port | AltairOne proxy server port | commented, please uncomment to add value |
https://docs.cambridgesemantics.com
The following information was extracted from the containerfile and other sources.
Summary | Graph Studio® Operator, ubi9 Image |
Description | Graph Studio® Operator lets a user deploy and manage life-cycle of Graph Studio® Agent and Server |
Provider | Cambridge Semantics |
Maintainer | https://altair.com/customer-support |
The following information was extracted from the containerfile and other sources.
Repository name | Graph Studio® Operator, ubi9 Image |
Image version | 3.1.3 |
Architecture | amd64 |
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running