I find the Operator's logs to be quite useful as it's running Ansible it outputs detailed information about what it's doing and tracking down the specific failure is fairly straight forward.
Kubernetes is definitely a learning curve, though. It's important to check all the instructions because there are a few secrets, etc., that need to be created manually to store db passwords, etc. I've found that once I understand how my K8s cluster is set up, getting the CP4Auto deploy to work is pretty straight forward. But we got stuck a lot the first few tries because we weren't understanding how our specific Ingress setup worked or storage like you described.
I did find that things were smoother and easier using a standard OpenShift cluster than when I tried other kinds of K8s (even something like IBM's ROKS was quirky).
Definitely a brave new world...
------------------------------
Eric Walk
Senior Technical Architect
O: 617-453-9984 M: 617-855-9255 | NASDAQ: PRFT | Perficient.com
------------------------------
Original Message:
Sent: Thu November 12, 2020 08:15 AM
From: Timo-Joel Piippola
Subject: Cloud Pak for Automation deployment
Hi
What kind experiences you people have with this operator and pattern based deployment? Are things working smoothly and fast? I am little bit struggling with AWS based environment with problems with podman( solved) and now with using gp2 as storage class. I am using latest 20.0.2.1 resources from cert-kubernetes github. Missing good old debugging and logs option.
------------------------------
-Timo-Joel
------------------------------