Forum Discussion

jerewis's avatar
jerewis
Novice I
3 years ago
Solved

Greetings: Deploying for a customer within POC..

Greetings: Deploying for a customer within POC.. PW on OCP 4.10.
PORTWORX DATA SERVICES
PX-BACKUP
PX-DR
PX-ENTERPRISE
  • ckennedy's avatar
    ckennedy
    3 years ago
    jerewis Hey Jeremy, when you are ready to try deploying again, please ping me here. I am more than happy to help out and figure out what is happening. By default, OCP usually installs the operator to a default namespace, I want to say ‘operators-system’, but is scoped so that the StorageCluster CRD can be read from any namespace in the cluster. I would recommend letting the operator go where RH want’s it, then create a namespace for Portworx. In that namespace create the vSphere secret and apply the StorageCluster spec.
  • jerewis's avatar
    jerewis
    Novice I
    3 years ago
    23 of 32 steps done. Deploying new virgin cluster also to set baseline
  • jerewis's avatar
    jerewis
    Novice I
    3 years ago
    Update status Update to 4.10.10 in progress https://console-openshift-console.apps.os01.penguinpages.local/k8s/cluster/config.openshift.io~v1~ClusterVersion/version#conditions|View conditions Channel Chttps://console-openshift-console.apps.os01.penguinpages.local/settings/cluster/clusteroperators|lusterOperators 31 of 32
  • jerewis's avatar
    jerewis
    Novice I
    3 years ago
    it failed again.. but tracked down that issue.. it was configuration on my side. Let me get a baseline here better. Upgrade failed: so redoing that cluster.... and other issue was ran my small home cluster out of resources .. so can't blame K8 for that. Let me regroup on latest / fresh install and I will post. THx for jumping in and finding resource
  • ckennedy's avatar
    ckennedy
    Novice I
    3 years ago
    jerewis Hey Jeremy, when you are ready to try deploying again, please ping me here. I am more than happy to help out and figure out what is happening. By default, OCP usually installs the operator to a default namespace, I want to say ‘operators-system’, but is scoped so that the StorageCluster CRD can be read from any namespace in the cluster. I would recommend letting the operator go where RH want’s it, then create a namespace for Portworx. In that namespace create the vSphere secret and apply the StorageCluster spec.
  • tlapp's avatar
    tlapp
    Novice I
    3 years ago
    I just deployed PX 2.10.0 via operator 1.8.0 (from operator hub) on OCP 4.10.11 No issues. I'm here too when you give it the next go.