Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Upgrade CP4I to 2023.4 #310

Merged
merged 1 commit into from
Dec 15, 2023
Merged

feat: Upgrade CP4I to 2023.4 #310

merged 1 commit into from
Dec 15, 2023

Conversation

nastacio
Copy link
Member

@nastacio nastacio commented Dec 15, 2023

closes: #265

Description of changes:

  • Upgrades CP4I to version 2023.4

Output of argocd app list command or screenshot of the Argo CD Application synchronization window showing successful application of changes in this branch.

 argocd app list
NAME                                  CLUSTER                         NAMESPACE         PROJECT               STATUS  HEALTH   SYNCPOLICY  CONDITIONS  REPO                                        PATH                                    TARGET
openshift-gitops/argo-app             https://kubernetes.default.svc  openshift-gitops  argocd-control-plane  Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/argocd                           265-cp4i-2023-4
openshift-gitops/cp-shared-app        https://kubernetes.default.svc  ibm-cloudpaks     default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/argocd-cloudpaks/cp-shared       265-cp4i-2023-4
openshift-gitops/cp-shared-operators  https://kubernetes.default.svc  ibm-cloudpaks     default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/cloudpaks/cp-shared/operators    265-cp4i-2023-4
openshift-gitops/cp4i-apic            https://kubernetes.default.svc  cp4i              default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/cloudpaks/cp4i/install-apic      265-cp4i-2023-4
openshift-gitops/cp4i-app             https://kubernetes.default.svc  cp4i              default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/argocd-cloudpaks/cp4i            265-cp4i-2023-4
openshift-gitops/cp4i-mq              https://kubernetes.default.svc  cp4i              default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/cloudpaks/cp4i/install-mq        265-cp4i-2023-4
openshift-gitops/cp4i-platform        https://kubernetes.default.svc  cp4i              default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/cloudpaks/cp4i/install-platform  265-cp4i-2023-4
openshift-gitops/cp4i-prereqs         https://kubernetes.default.svc  cp4i              default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops.git  config/cloudpaks/cp4i/install-prereqs   265-cp4i-2023-4

@nastacio nastacio added enhancement New feature or request chore General upkeep of the repository, not a bug or enhancement labels Dec 15, 2023
@nastacio nastacio self-assigned this Dec 15, 2023
Signed-off-by: Denilson Nastacio <[email protected]>
@nastacio nastacio marked this pull request as ready for review December 15, 2023 20:22
@nastacio
Copy link
Member Author

The only problem identified in the test runs, which is not specific to this repository, is that CP4I 2023.4 has an identified problem with ROKS 4.14 (released on the same day as CP4I) .

@nastacio nastacio merged commit 1d049ca into main Dec 15, 2023
3 checks passed
@nastacio nastacio deleted the 265-cp4i-2023-4 branch December 15, 2023 20:23
@nastacio
Copy link
Member Author

🎉 This PR is included in version 0.36.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@nastacio nastacio added the released The issue or pull request is added to a release label Dec 15, 2023
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The repo already has validation for the Queue Manager using a JMS client and this Node-based setup is no longer necessary.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The repo already has validation for the Queue Manager using a JMS client and this Node-based setup is no longer necessary.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The repo already has validation for the Queue Manager using a JMS client and this Node-based setup is no longer necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore General upkeep of the repository, not a bug or enhancement enhancement New feature or request released The issue or pull request is added to a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: Update Cloud Pak for Integration to the 2023.4 release
1 participant