Hello,
My goal is to deploy App Connect in IBM IKS using App connect operator. So far, I have deployed subscription & app connect operator. Now, I'm struck with dashboard deployment.
In IBM Kubernetes cluster, there are no file-based storages classes available, not sure if this is ideal or not. So, then want to use PVC claim. Here are my yaml files.
PV :
apiVersion: v1
kind: PersistentVolume
metadata:
name: ibm-appconn-pv
namespace: ibm-appconn-ns
spec:
storageClassName: manual
capacity:
storage: 10Gi
accessModes:
- ReadWriteMany
hostPath:
path: "/mnt/data"
PVC:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: ibm-appconn-pvc
namespace: ibm-appconn-ns
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi
Dashboard:
apiVersion: appconnect.ibm.com/v1beta1
kind: Dashboard
metadata:
name: ace-dashboard
namespace: ibm-appconn-ns
spec:
license:
accept: true
license: L-KSBM-C37JH7
use: AppConnectEnterpriseNonProduction
pod:
containers:
content-server:
resources:
limits:
cpu: 250m
memory: 512Mi
requests:
cpu: 50m
memory: 50Mi
control-ui:
resources:
limits:
cpu: 250m
memory: 512Mi
requests:
cpu: 50m
memory: 125Mi
replicas: 3
storage:
size: 5Gi
type: persistent-claim
claimName: ibm-appconn-pvc
useCommonServices: false
version: 12.0.1.0-r1
Error while deploying dashboard is : Error from server: error when creating "appconn-dashboard.yaml": admission webhook "validate.storage.appconnect.ibm.com" denied the request: [A storage class must be provided when using persistent storage - cp4i.runtime.
check]
According to the documentation about the dashboard resource, when spec.storage.type is set to persistent-claim, either spec.storage.claimName or spec.storage.class is required. So, logically the above dashboard resource definition should work.
Any reply is appreciated.
Thanks !
------------------------------
Sujeeth Pakala
------------------------------