Skip to content

Conversation

@syan-tibco
Copy link
Collaborator

This pull request introduces support for deploying and upgrading the CP AI Agent (tibco-cp-ai-agent) as part of the platform provisioner Helm charts and automation recipes. It also adds resource configuration options for ElasticSearch, Kibana, and APM in the observability (O11y) stack, updates ingress controller defaults to traefik for automation, and bumps several version tags. The changes enhance flexibility and compatibility with recent platform releases and UI changes.

CP AI Agent Integration:

  • Added options and recipe logic to deploy and upgrade the CP AI Agent (tibco-cp-ai-agent) in both on-prem and upgrade workflows, including chart version selection, install/upgrade toggles, and Helm chart configuration in pp-deploy-cp-core-on-prem.yaml and pp-deploy-cp-core-upgrade.yaml. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]
  • Bumped chart version to 1.13.11 in provisioner-config-local/Chart.yaml to reflect new features.

Observability (O11y) Resource Configuration:

  • Introduced resource request and limit settings for ElasticSearch, Kibana, and APM in the O11y stack, allowing for fine-grained control over CPU and memory usage in pp-o11y-full.yaml. [1] [2] [3] [4]

Automation and UI Compatibility:

  • Changed default ingress controller to traefik in automation config and environment files, and updated automation logic to handle new dropdown UI for ingress controller selection in BMDP creation. [1] [2] [3]

Version Updates and Documentation:

  • Updated automation and base image tags to latest versions (1.6.11-auto-on-prem-jammy), and documented the automation support for the 1.13 release in the changelog and version files. [1] [2] [3] [4]

Cloud Deployment Minor Fix:

  • Fixed GCP project ID variable in GKE deployment recipe for correct cloud provisioning.

@syan-tibco syan-tibco merged commit 4d70ab1 into main Dec 9, 2025
1 check passed
@syan-tibco syan-tibco deleted the releases/202550 branch December 9, 2025 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants