Closed goetzrieger closed 4 months ago
Why ODF? Demo.redhat.com is running on AWS you can use cloud storage / s3 from aws?!
We usually try to avoid using native Hyperscaler services where possible in our workshops, to make the workshop portable/hybrid.
If it's a demo.redhat.com env, is the chance that big to deploy the env somewhere else?
Fair point. On the other hand we already have this setup fully automated in Ansible. Switching to AWS S3 would mean additional work. Let's discuss this offline.
Skupper connection is missing.
Installed operators:
[lab-user@bastion ~]$ oc get installplan -A
NAMESPACE NAME CSV APPROVAL APPROVED
gitea-operator install-zslmv gitea-operator.v2.0.1 Automatic true
openshift-devspaces install-524m8 devworkspace-operator.v0.27.0-0.1714987663.p Automatic true
openshift-operators install-26vsv openshift-gitops-operator.v1.12.3 Automatic true
openshift-operators install-jckp8 web-terminal.v1.10.0 Automatic true
openshift-operators install-qmgtf openshift-pipelines-operator-rh.v1.14.4 Automatic true
openshift-storage install-mk55v ocs-operator.v4.15.2-rhodf Automatic true
redhat-ods-operator install-vj2wq rhods-operator.2.8.2 Automatic true
Including ARM Nodes for multi-arch build:
[lab-user@bastion ~]$ oc get nodes -L kubernetes.io/arch
NAME STATUS ROLES AGE VERSION ARCH
ip-10-0-23-42.eu-west-1.compute.internal Ready worker 3h37m v1.28.9+416ecaf amd64
ip-10-0-24-201.eu-west-1.compute.internal Ready control-plane,master 3h55m v1.28.9+416ecaf amd64
ip-10-0-28-221.eu-west-1.compute.internal Ready worker 3h37m v1.28.9+416ecaf amd64
ip-10-0-29-5.eu-west-1.compute.internal Ready arm,worker 2m20s v1.28.9+416ecaf arm64
ip-10-0-7-216.eu-west-1.compute.internal Ready worker 3h45m v1.28.9+416ecaf amd64
[lab-user@bastion ~]$
Skupper is handled via #15 and #16
Use DevSecOps WS Automation to: