IBM Cloud Private

https://www.ibm.com/docs/en/cloud-private/3.2.0
Admin
IBM Cloud Private is a platform for developing, deploying, and managing cloud-native applications...
Tokens:781,612
Snippets:6,870
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### Example: Install WordPress Helm Chart (Bash)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=guide-installing-helm-cli-helm

An example of installing the WordPress chart using Helm. This command creates a release named 'my-wordpress'.

```bash
helm install --name=my-wordpress stable/wordpress --tls

```

--------------------------------

### Example: Launch Cloud Foundry Deployment Tool

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=icpcf-installing-cloud-private-cloud-foundry-cloud-foundry-deployment-tool

This example shows how to launch the Cloud Foundry deployment tool with specific parameters for installation. It includes parameters for naming, BOM file, data directory, license acceptance, IP restriction, and UI port.

```bash
./launch.sh -n IBMCloudPrivate -b ./BOM.yml -c /home/user/data -e LICENSE=accept -ih 10.10.1.2 -pui 9090

```

--------------------------------

### Install Git Tools and Clone Horizon Examples Repository

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=examples-model-management-system

This command installs necessary tools (git, make, jq) and clones the Horizon examples repository for developing edge services. It is designed for Linux operating systems and requires sudo privileges. The cloned repository contains various edge service code implementation examples, including the model management system service example.

```bash
sudo apt install -y git make jq
cd ~
git clone https://github.com/open-horizon/examples.git
```

--------------------------------

### Launch Installer Script for Upgrade

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=guide-upgrading-cloud-private-cloud-foundry

Executes the launch script to start the IBM Cloud Private installer container for an upgrade. Requires environment name and configuration directory. Accepts license acceptance.

```shell
./launch.sh -n <environment_name> -c <installation_configuration_directory> -e LICENSE=accept

```

--------------------------------

### Get help for hzn command and sub-commands

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=started-registering-your-edge-machines

This snippet demonstrates how to access help documentation for the `hzn` command and its sub-commands using the `--help` flag. It is useful for understanding the available options and parameters for various `hzn` operations.

```bash
hzn --help
hzn node --help
hzn exchange pattern --help
```

--------------------------------

### Run Node.js Application Locally

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=foundry-working-service-broker-nodejs-starter-app

Starts the Node.js application. After installing dependencies, this command executes the start script defined in `package.json`, typically launching the application on a local development server.

```bash
npm start
```

--------------------------------

### Install and Setup encryptfs on Ubuntu

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=foundry-post-installation-steps-cloud-private-cloud

Commands to install the encryptfs utility on Ubuntu and set up a private encrypted directory. This is used for encrypting the installation configuration data at rest. Requires root privileges.

```bash
# Ubuntu
sudo apt-get install ecryptfs-utils
encryptfs-setup-private
```

--------------------------------

### Configure Master Nodes as Proxy Nodes (YAML Example)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=networking-ingress-resources

Example configuration for the 'config.yaml' file to designate master nodes as proxy nodes. This is useful when using an external load balancer and requires labeling master nodes before installation.

```yaml
[master]
172.21.13.110
172.21.13.111
172.21.13.112

[proxy]
172.21.13.110
172.21.13.111
172.21.13.112

```

--------------------------------

### Create Installation Directory and Change Directory

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=openshift-installing-cloud-private

This command sequence creates a directory for IBM Cloud Private configuration files and then changes the current directory to the newly created one. This is a standard setup step for configuration management.

```shell
mkdir /opt/ibm-cloud-private-rhos-3.2.0; \
 cd /opt/ibm-cloud-private-rhos-3.2.0
```

--------------------------------

### Enable verbose output for hzn commands

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=started-registering-your-edge-machines

This snippet shows how to use the `--verbose` (or `-v`) flag with `hzn` commands to get more detailed output. This is particularly helpful for understanding the underlying REST API calls that the `hzn` command makes, which can aid in debugging and deeper system analysis.

```bash
hzn node list -v
```

--------------------------------

### Configure Hosts File for GlusterFS with Dedicated Nodes

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=glusterfs-configuring-during-cloud-private-installation

Example configuration for the /<installation_directory>/cluster/hosts file when using dedicated nodes for GlusterFS. This setup separates GlusterFS nodes from worker nodes.

```yaml
[worker]
2.2.2.2
...
2.2.2.9
.
.
[hostgroup-glusterfs]
6.6.6.6
...
6.6.6.9


```

--------------------------------

### List Available Edge Service Deployment Patterns

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=started-registering-your-edge-machines

This command displays the available sample edge service deployment patterns within the IBM organization in the Horizon exchange. It helps in identifying suitable patterns, like 'helloworld', for deployment.

```bash
hzn exchange pattern list IBM/
```

--------------------------------

### Prepare Installation Directory for Upgrade (Bash)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=upgrading-cloud-private-ce

Creates a new installation directory and copies the cluster configuration from a previous installation. It also removes old upgrade-related files. Ensure to replace '/<installation_directory>' with your actual previous installation path.

```bash
mkdir -p /opt/ibm-cloud-private-3.2.0
cd /opt/ibm-cloud-private-3.2.0
cp -r /<installation_directory>/cluster .
sudo rm -rf .upgrade upgrade_version

```

--------------------------------

### Troubleshoot Tiller Start Failure: Get Container Logs (Bash)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=upgrade-installation-failed-waiting-tiller-start

This command retrieves the logs for a specific Tiller container using its ID. This is useful for diagnosing installation failures where the 'address already in use' error is observed, indicating a port conflict on Tiller port 44134.

```Bash
docker logs <tiller_container_id>
```

--------------------------------

### Create a Simple Dockerfile for 'Hello, world'

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=examples-quick-start-guide

This snippet provides the content for a basic Dockerfile. It uses the `alpine:latest` image and sets a command to continuously log 'Hello, world.' every few seconds. This is useful for creating a minimal service for testing.

```dockerfile
FROM alpine:latest
CMD while :; do echo "Hello, world."; sleep 3; done
```

--------------------------------

### Installing and Initializing IBM Event Streams Plugin (Bash)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=started-host-cpu-load-percentage

This sequence of commands installs the IBM Event Streams cloudctl plugin, initializes it, creates a topic named 'cpu2msghub' with specified partitions and replicas, and then lists all available topics.

```bash
cloudctl plugin install <es-plugin-file>
cloudctl es init
cloudctl es topic-create cpu2msghub -p 2 -r 1
cloudctl es topics
```

--------------------------------

### Deploy Sample Web Server (Kubernetes/Shell)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=preview-adding-windows-worker-node-cloud-private-cluster

This snippet demonstrates deploying a sample web server using a Kubernetes manifest. It includes downloading the manifest file and applying it to the cluster. This process requires `kubectl` and `wget`.

```shell
# wget https://raw.githubusercontent.com/Microsoft/SDN/master/Kubernetes/flannel/l2bridge/manifests/simpleweb.yml -O win-webserver.yaml

# kubectl apply -f win-webserver.yaml
```

--------------------------------

### Troubleshoot Tiller Start Failure: Get Container ID (Bash)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=upgrade-installation-failed-waiting-tiller-start

This command helps identify the container ID for the Tiller process on master nodes. It is a prerequisite for checking Tiller logs when installation fails due to Tiller port conflicts. Run this command on each master node in a high availability cluster.

```Bash
docker ps -a | grep tiller
```

--------------------------------

### Example Etcdctl3 Output for Decrypted Secret

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=administration-managing-secrets

This is an example of the output from the `etcdctl3 get` command, showing that the secret value is stored as plain text. This confirms that the decryption process has been completed successfully.

```json
"ClusterID" : 16723368499499280303
"MemberID" : 15696589318412288662
"Revision" : 862012
"RaftTerm" : 5
"Key" : "/registry/secrets/kube-system/platform-auth-idp-credentials"
"CreateRevision" : 4595
"ModRevision" : 861920
"Version" : 10
"Value" : "k8s\x00\n\f\n\x02v1\x12\x06Secret\x12\xa4\x01\nf\n\x1dplatform-auth-idp-credentials\x12\x00\x1a\vkube-system"\x00*$31a7a864-bd75-11e8-831a-005056a2e1282\x008\x00B\b\b\xef̒\xdd\x05\x10\x00z\x00\x12\x18\n\x0eadmin_password\x12\x06admin\x12\x18\n\x0eadmin_username\x12\x06admin\x1a\x06Opaque\x1a\x00"\x00"
"Lease" : 0
"More" : false
"Count" : 1
```

--------------------------------

### Update Kubelet Service File Content Example

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=cvcp-configuring-vsphere-cloud-provider-after-cloud-private-installation

This example demonstrates the expected content of the `/etc/systemd/system/kubelet.service` file after the `--cloud-provider=vsphere` flag has been added. It shows the flag integrated within the `ExecStart` command, alongside other Kubelet configurations.

```ini
[Unit]
Description=Kubelet Service
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/etc/environment
ExecStart=/opt/kubernetes/hyperkube kubelet \
... \
 --cloud-provider=vsphere \
...
```

--------------------------------

### Create File System

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=installation-encrypting-volumes-by-using-dm-crypt

Creates a file system on the opened logical volume, preparing it for data storage. This example uses `mkfs.xfs`, but other file systems like ext4 can also be used.

```bash
mkfs.xfs /dev/mapper/<name of the logical volume>
```

--------------------------------

### Clone Sample App with Git

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=foundry-working-user-provided-services-liberty-starter-app

This command clones the sample application from a GitHub repository. It requires Git to be installed and configured on your system. The output is the local copy of the sample application.

```bash
git clone https://github.com/IBM-Bluemix/get-started-java
```

--------------------------------

### Starting HAProxy Service

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=installation-setting-up-external-load-balancer

Command to start the HAProxy service on the load balancer node. Ensure HAProxy is installed and configured before running this command.

```bash
systemctl start haproxy
```

--------------------------------

### Customizing Cluster Scope Policy Before Installation (YAML)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=images-enforcing-container-image-security

This YAML snippet shows how to pre-define a cluster-scope image policy in the config.yaml file before installing IBM Cloud Private. This example allows all images from the 'quay.io' repository.

```yaml
image-security-enforcement:
  clusterImagePolicy:
    - name: "quay.io/*"
      policy:


```

--------------------------------

### Extension Folder Structure Example

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=foundry-using-extensions-in-cloud-private-cloud

Example folder structure for a deployment extension. The manifest file should be in the root, and script files can be organized in subfolders. Ensure script parameters reference correct relative paths.

```text
extension-manifest.yml
scripts/
scripts/success.sh
scripts/README.md
```

--------------------------------

### Populate Sample Services

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=devices-installing-edge-computing-infrastructure

Downloads and executes a script to populate sample services into the IBM Edge Computing for Devices exchange. This script is hosted on GitHub and is essential for testing and demonstrating service deployment.

```shell
curl https://raw.githubusercontent.com/open-horizon/examples/v3.2.0/tools/exchangePublishScript.sh | bash
```

--------------------------------

### Launch Deployment with UI Configuration

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=foundry-configuring-availability-zones

This script launches the deployment process using a specified UI configuration file. It's used after initial configuration steps.

```bash
./launch_deployment.sh -c uiconfig.yml

```

--------------------------------

### Run IBM Cloud Private-CE Installation

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=installing-cloud-private-cloud-native-enterprise-community-editions

This command starts the IBM Cloud Private Community Edition installation. It utilizes the 'ibmcom/icp-inception:3.2.0' Docker image and requires the LICENSE and LANG environment variables to be set. The LANG variable should be set to a supported language.

```shell
sudo docker run -e LICENSE=view -e LANG=$LANG ibmcom/icp-inception:3.2.0
```

--------------------------------

### Example platform-auth-idp configmap content

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=configurations-configuring-access-identity-token-validity

This is an example of the content within the `platform-auth-idp` configmap. Users will modify this file to change token validity settings. Lines starting with '#' are comments and are ignored.

```yaml
# Please edit the following object. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.

```

--------------------------------

### Enable Istio in IBM Cloud Private during installation (YAML)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=guide-enable-istio-cloud-private

This YAML configuration snippet shows how to enable Istio as a management service during the IBM Cloud Private cluster installation. Modify the `config.yaml` file by setting the `istio` parameter to `enabled`. This ensures Istio is installed along with the cluster, simplifying the setup process.

```yaml
management_services:
  istio: enabled
  vulnerability-advisor: disabled
  storage-glusterfs: disabled
  storage-minio: disabled

```

--------------------------------

### Compile and Run CUDA deviceQuery Sample

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=upgrade-nvidia-gpu-driver-fails-initialize

This snippet shows the process of compiling the `deviceQuery.cpp` file using the `nvcc` compiler and then running the compiled `deviceQuery` executable. It navigates to the sample's directory, compiles the source code, and executes the binary. The output confirms the CUDA driver and runtime versions, along with detected CUDA-capable devices.

```bash
kubectl exec -it cuda-vector-add-858b9445cb-mdlrp bash
root@cuda-vector-add-858b9445cb-mdlrp:/usr/local/cuda-10.0/samples/0_Simple/vectorAdd# cd ../../1_Utilities/deviceQuery
root@cuda-vector-add-858b9445cb-mdlrp:/usr/local/cuda-10.0/samples/1_Utilities/deviceQuery# make
/usr/local/cuda-10.0/bin/nvcc -ccbin g++ -I../../common/inc  -m64    -gencode arch=compute_30,code=sm_30 -gencode arch=compute_35,code=sm_35 -gencode arch=compute_37,code=sm_37 -gencode arch=compute_50,code=sm_50 -gencode arch=compute_52,code=sm_52 -gencode arch=compute_60,code=sm_60 -gencode arch=compute_61,code=sm_61 -gencode arch=compute_70,code=sm_70 -gencode arch=compute_75,code=sm_75 -gencode arch=compute_75,code=compute_75 -o deviceQuery.o -c deviceQuery.cpp
/usr/local/cuda-10.0/bin/nvcc -ccbin g++   -m64      -gencode arch=compute_30,code=sm_30 -gencode arch=compute_35,code=sm_35 -gencode arch=compute_37,code=sm_37 -gencode arch=compute_50,code=sm_50 -gencode arch=compute_52,code=sm_52 -gencode arch=compute_60,code=sm_60 -gencode arch=compute_61,code=sm_61 -gencode arch=compute_70,code=sm_70 -gencode arch=compute_75,code=sm_75 -gencode arch=compute_75,code=compute_75 -o deviceQuery deviceQuery.o
mkdir -p ../../bin/ppc64le/linux/release
cp deviceQuery ../../bin/ppc64le/linux/release
./deviceQuery
```

--------------------------------

### Calico CLI Configuration Script Example

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=calico-installing-cli-calicoctl

An example shell script that sets the necessary environment variables for `calicoctl` to connect to the etcdv3 datastore. This script can be sourced or executed to configure the `calicoctl` environment for the current session or persistent use.

```sh
#!/bin/sh
export ETCD_CERT_FILE=/etc/cfc/conf/etcd/client.pem
export ETCD_CA_CERT_FILE=/etc/cfc/conf/etcd/ca.pem
export ETCD_KEY_FILE=/etc/cfc/conf/etcd/client-key.pem
export ETCD_ENDPOINTS=https://<Cluster Master Host>:4001

```

--------------------------------

### Configure and Install GlusterFS Client on RHEL for Power (ppc64le)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=persistentvolume-creating-glusterfs

Sets up a repository and installs the GlusterFS client on RHEL Linux on Power (ppc64le). This is necessary for systems with this architecture to connect to external GlusterFS storage.

```shell
[centos-gluster40]
name=CentOS-$releasever - Gluster 4.0
baseurl=https://buildlogs.centos.org/centos/7/storage/$basearch/gluster-4.0/
gpgcheck=0
enabled=1

sudo yum install glusterfs-client
```

--------------------------------

### Check libreswan IPsec Configuration (RHEL)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=networks-ipsec-mesh-troubleshooting

Displays the content of libreswan IPsec configuration files on RHEL systems. Used to verify the IPsec setup after installation.

```bash
cat /etc/ipsec.conf
cat /etc/ipsec.d/ipsec-libreswan.conf
```

--------------------------------

### Get WLP_CLIENT_ID using kubectl

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=configurations-customizing-cluster-access-url

This command retrieves the WLP_CLIENT_ID from the platform-oidc-credentials secret in the kube-system namespace. It requires `kubectl` to be installed and configured for the cluster. The output is the base64 decoded WLP_CLIENT_ID.

```bash
WLP_CLIENT_ID=$(kubectl -n kube-system get secret platform-oidc-credentials -o yaml | grep WLP_CLIENTID | awk '{ print $2}' | base64 --decode)

```

--------------------------------

### Build and Run Java App Locally with Maven and Liberty

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=foundry-working-user-provided-services-liberty-starter-app

This section details how to build the Java source code using Maven and run the application locally on a Liberty server. It requires Maven and the Liberty runtime to be installed. The commands change the directory, clean and install the project, and then run the Liberty server.

```bash
cd get-started-java

```

```bash
mvn clean install

```

```bash
mvn install liberty:run-server

```

--------------------------------

### Update Kubelet Service File with Cloud Provider Flags

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=cvcp-configuring-vsphere-cloud-provider-after-cloud-private-installation

This example demonstrates how to integrate the cloud provider flags into the `/etc/systemd/system/kubelet.service` file within the `[Service]` section. It shows the complete structure of the service file with the added parameters.

```systemd
[Unit]
Description=Kubelet Service
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=-/etc/environment
ExecStart=/opt/kubernetes/hyperkube kubelet \
 ...
  --cloud-provider=vsphere \
  --cloud-config=/etc/cfc/conf/vsphere.conf \
       
 ...

```

--------------------------------

### Get Helm Release Name

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=cfsymmc-configure-failover-settings-your-multicloud-manager-hub-clusters

This command retrieves the name of the installed Helm release for multicluster components. It uses `helm list --tls` and filters the output for 'multicluster'.

```shell
helm list --tls |grep multicluster
```

--------------------------------

### Install cryptsetup on Ubuntu

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=installation-encrypting-volumes-by-using-dm-crypt

Installs the 'cryptsetup' package on Ubuntu systems, which is a prerequisite for encrypting directories in IBM Cloud Private. This command should be run as a root user.

```bash
apt-get install cryptsetup
```

--------------------------------

### Configure etcd Space Quota Before IBM Cloud Private Installation (YAML)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=administration-managing-etcd-clusters

This snippet demonstrates how to configure the etcd space quota using the `--quota-backend-bytes` flag in the `cluster/config.yaml` file before installing IBM Cloud Private. The example sets the quota to 1 GB (1073741824 bytes).

```yaml
etcd_extra_args: ["--quota-backend-bytes=1073741824"]
```

--------------------------------

### Prepare Cluster for Upgrade (Docker)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=upgrading-cloud-private-ce

Runs a Docker container to prepare the cluster for the upgrade. It mounts the current cluster directory and accepts the license. Ensure you are in the cluster directory before running this command.

```bash
sudo docker run -e LICENSE=accept --net=host --rm -t -v "$(pwd)":/installer/cluster \
ibmcom/icp-inception:3.2.0 upgrade-prepare

```

--------------------------------

### Configure Persistent Volume for Prometheus using Labels

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=logging-cloud-private-monitoring

Example of defining a PersistentVolume with labels for Prometheus component identification. This demonstrates how to manually create a PersistentVolume before installing the monitoring service, ensuring data persistence.

```yaml
apiVersion: v1
kind: PersistentVolume
metadata:
    name: monitoring-prometheus-pv
    labels:
        component: prometheus
.......
```

--------------------------------

### Get Minio Helm Release Configuration

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=minio-upgrading

Retrieves the configuration value of an installed Helm release for Minio. This command filters the output of 'helm list --tls' to find the specific Minio release.

```bash
helm list --tls | grep mini
```

```bash
helm get values <Helm release name> --tls > values-minio.yaml
```

```bash
helm get values minio --tls > values-minio.yaml
```

--------------------------------

### Logo Path Configuration Example

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=ayc-configuring-your-logo-in-cloud-private-management-console

This example shows how to specify the path for your logo image within the UI configuration. The path can point to various image formats like SVG, PNG, or JPG, and should be accessible by the server.

```json
"path": "http(s)://<server-stored-images>/path/to/logo.svg|png|jpg"
```

--------------------------------

### Example Docker Registry Login (No Entitlements)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=charts-adding-featured-applications-clusters-in-airgap-environment

An example of how to log in to a Docker registry, specifically for a registry named `mycluster.icp:8500`, when no product entitlements are required.

```bash
docker login mycluster.icp:8500

```

--------------------------------

### Configure etcd Space Quota After IBM Cloud Private Installation (JSON)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=administration-managing-etcd-clusters

This snippet shows how to configure the etcd space quota after IBM Cloud Private has been installed. It involves editing the `/etc/cfc/pods/etcd.json` file on the master node and adding the `--quota-backend-bytes` argument to the etcd command. The example sets the quota to 1 GB.

```json
"--quota-backend-bytes=1073741824",
```

--------------------------------

### Preinstallation Configuration of Prometheus via config.yaml

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=logging-cloud-private-monitoring

Example of configuring Prometheus parameters like scrape interval, evaluation interval, retention, and memory limits within the config.yaml file before installing the monitoring service in IBM Cloud Private.

```yaml
monitoring:
  prometheus:
    scrape_Interval: 1m
    evaluation_Interval: 1m
    retention: 24h
    resources:
      limits:
        memory: 4096Mi
```

--------------------------------

### Create Project Directory and Navigate

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=examples-quick-start-guide

This snippet shows how to create a new project directory for your IBM Edge Computing for Devices project and then navigate into it using the command line. This is the initial step for setting up your development environment.

```shell
mkdir quickstart
cd quickstart
```

--------------------------------

### Install Helm Chart (Bash)

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=guide-installing-helm-cli-helm

Installs a specified Helm chart from a repository. Replace `release_name` with your desired release name and `chart_in_repo` with the chart name.

```bash
helm install --name=release_name stable/chart_in_repo --tls

```

--------------------------------

### Enable GlusterFS Storage in config.yaml

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=glusterfs-configuring-during-cloud-private-installation

Example configuration for the /<installation_directory>/cluster/config.yaml file to enable GlusterFS storage as a management service. This involves setting 'storage-glusterfs: enabled' under the 'management_services' section.

```yaml
management_services:
  istio: disabled
  vulnerability-advisor: disabled
  storage-glusterfs: enabled
  storage-minio: disabled


```

--------------------------------

### Get Minio Server Info via kubectl exec

Source: https://www.ibm.com/docs/en/cloud-private/3.2.0/index_topic=minio-verifying-setup

Executes a command within the 'minioclient' pod to retrieve information about the Minio server. This verifies the server's status, version, and storage usage.

```bash
kubectl exec minioclient mc admin info myminio
```
Tokens:
Raw