Closed carlmes closed 1 month ago
Testing on a demo.redhat.com blank cluster.
❯ ./bootstrap.sh
Validating CLI tool: oc
/opt/homebrew/bin/oc
auto-complete: . <(oc completion bash)
Client Version: 4.16.13
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.16.15
Kubernetes Version: v1.29.8+f10c92d
Validating CLI tool: kustomize
/opt/homebrew/bin/kustomize
auto-complete: . <(kustomize completion bash)
v5.4.3
Kubernetes control plane is running at https://api.cluster-f682c.f682c.sandbox618.opentlc.com:6443
kube:admin
Checking if GitOps Operator is already installed and running
Installing GitOps Operator.
namespace/openshift-gitops-operator created
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin created
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin created
operatorgroup.operators.coreos.com/openshift-gitops-operator created
subscription.operators.coreos.com/openshift-gitops-operator created
.namespace/openshift-gitops-operator unchanged
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
operatorgroup.operators.coreos.com/openshift-gitops-operator unchanged
subscription.operators.coreos.com/openshift-gitops-operator unchanged
.namespace/openshift-gitops-operator unchanged
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
operatorgroup.operators.coreos.com/openshift-gitops-operator unchanged
subscription.operators.coreos.com/openshift-gitops-operator unchanged
.namespace/openshift-gitops-operator unchanged
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
operatorgroup.operators.coreos.com/openshift-gitops-operator unchanged
subscription.operators.coreos.com/openshift-gitops-operator unchanged
.namespace/openshift-gitops-operator unchanged
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
operatorgroup.operators.coreos.com/openshift-gitops-operator unchanged
subscription.operators.coreos.com/openshift-gitops-operator unchanged
.namespace/openshift-gitops-operator unchanged
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
operatorgroup.operators.coreos.com/openshift-gitops-operator unchanged
subscription.operators.coreos.com/openshift-gitops-operator unchanged
.namespace/openshift-gitops-operator unchanged
serviceaccount/job-gitops-console-plugin created
clusterrole.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
clusterrolebinding.rbac.authorization.k8s.io/job-gitops-console-plugin unchanged
configmap/job-gitops-console-plugin created
job.batch/job-gitops-console-plugin created
operatorgroup.operators.coreos.com/openshift-gitops-operator unchanged
subscription.operators.coreos.com/openshift-gitops-operator unchanged
Waiting for deployment of the openshift-gitops-operator-controller-manager to begin...
NAME READY UP-TO-DATE AVAILABLE AGE
openshift-gitops-operator-controller-manager 0/1 1 0 13s
Waiting for openshift-gitops-operator-controller-manager to start...
deployment.apps/openshift-gitops-operator-controller-manager condition met
Waiting for openshift-gitops namespace to be created...
namespace/openshift-gitops condition met
Waiting for deployments to start...
deployment.apps/cluster condition met
Checking status of all openshift-gitops pods
Waiting for deployment/cluster state to be condition=Available...
deployment.apps/cluster condition met
Waiting for deployment/kam state to be condition=Available...
deployment.apps/kam condition met
Waiting for statefulset/openshift-gitops-application-controller state to be jsonpath={.status.readyReplicas}=1...
pod/openshift-gitops-application-controller-0 condition met
Waiting for deployment/openshift-gitops-applicationset-controller state to be condition=Available...
deployment.apps/openshift-gitops-applicationset-controller condition met
Waiting for deployment/openshift-gitops-redis state to be condition=Available...
deployment.apps/openshift-gitops-redis condition met
Waiting for deployment/openshift-gitops-repo-server state to be condition=Available...
deployment.apps/openshift-gitops-repo-server condition met
Waiting for deployment/openshift-gitops-server state to be condition=Available...
deployment.apps/openshift-gitops-server condition met
OpenShift GitOps successfully installed.
1) rhoai-eus-2.8-aws-gpu 3) rhoai-fast-aws-gpu 5) rhoai-stable-2.10
2) rhoai-eus-2.8 4) rhoai-fast 6) rhoai-stable-2.13
Please enter a number to select a bootstrap folder: 6
Selected: rhoai-stable-2.13
FORCE is set to
\e[33myq could not be found. We are unable to verify the branch of your repo.\e[0m
Apply overlay to override default instance
clusterrolebinding.rbac.authorization.k8s.io/openshift-gitops-application-controller-cluster-admin created
appproject.argoproj.io/cluster-config created
appproject.argoproj.io/gitops-config created
appproject.argoproj.io/operators-config created
appproject.argoproj.io/tenants created
application.argoproj.io/cluster-config-app-of-apps created
applicationset.argoproj.io/cluster-configs created
applicationset.argoproj.io/cluster-operators created
applicationset.argoproj.io/tenants created
Warning: resource argocds/openshift-gitops is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically.
argocd.argoproj.io/openshift-gitops configured
group.user.openshift.io/gitops-admins created
Checking status of all openshift-gitops pods
Waiting for deployment/cluster state to be condition=Available...
deployment.apps/cluster condition met
Waiting for deployment/kam state to be condition=Available...
deployment.apps/kam condition met
Waiting for statefulset/openshift-gitops-application-controller state to be jsonpath={.status.readyReplicas}=1...
pod/openshift-gitops-application-controller-0 condition met
Waiting for deployment/openshift-gitops-applicationset-controller state to be condition=Available...
deployment.apps/openshift-gitops-applicationset-controller condition met
Waiting for deployment/openshift-gitops-redis state to be condition=Available...
deployment.apps/openshift-gitops-redis condition met
Waiting for deployment/openshift-gitops-repo-server state to be condition=Available...
deployment.apps/openshift-gitops-repo-server condition met
Waiting for deployment/openshift-gitops-server state to be condition=Available...
deployment.apps/openshift-gitops-server condition met
Restart the application-controller to start the sync
pod "openshift-gitops-application-controller-0" deleted
Checking status of all openshift-gitops pods
Waiting for deployment/cluster state to be condition=Available...
deployment.apps/cluster condition met
Waiting for deployment/kam state to be condition=Available...
deployment.apps/kam condition met
Waiting for statefulset/openshift-gitops-application-controller state to be jsonpath={.status.readyReplicas}=1...
pod/openshift-gitops-application-controller-0 condition met
Waiting for deployment/openshift-gitops-applicationset-controller state to be condition=Available...
deployment.apps/openshift-gitops-applicationset-controller condition met
Waiting for deployment/openshift-gitops-redis state to be condition=Available...
deployment.apps/openshift-gitops-redis condition met
Waiting for deployment/openshift-gitops-repo-server state to be condition=Available...
deployment.apps/openshift-gitops-repo-server condition met
Waiting for deployment/openshift-gitops-server state to be condition=Available...
deployment.apps/openshift-gitops-server condition met
GitOps has successfully deployed! Check the status of the sync here:
https://openshift-gitops-server-openshift-gitops.apps.cluster-f682c.f682c.sandbox618.opentlc.com
Love the screenshots helping to verify the completed deployment btw!
Tasks in this pull request:
Review the release notes for 2.10-2.13 and identify any changes required for the AI Accelerator between 2.10 and 2.13: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/2-latest/html-single/release_notes/index
Update the AI Accelerator repo example for 2.10 to support 2.13: https://github.com/redhat-ai-services/ai-accelerator
Create a new overlay for stable-2.13 in the openshift-ai operator, instance, and aggregate folders: https://github.com/redhat-ai-services/ai-accelerator/tree/main/components/operators/openshift-ai/
Create new overlays for
rhoai-stable-2.13
andrhoai-stable-2.13-aws-gpu
that deploys the new 2.13 version for the cluster. Test all examples with 2.13 to ensure capabilities are still functional.Update the
rhoai-fast
channel with any required 2.13 features.Contribute the changes to the openshift-ai operator examples back to the gitops-catalog: https://github.com/redhat-cop/gitops-catalog