Add ArgoCD and Kustomize deployment #135
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a set of Kustomize manifests and example ArgoCD Applications for deploying OpenCHAMI management services and a test VM.
This stands up the test environment discussed in OpenCHAMI/ochami#47 (comment)
My intent is to use this as the main Kubernetes deployment system for OpenCHAMI services and to provision test environments for it, as a more batteries-included Kubernetes-flavored quickstart than we're reasonably able to handle with Helm.
Some functionality relies on as-yet unreleased code. We want to eventually get on officially released images, but need this environment to demonstrate that some changes work. In general, we should probably start making nightly and on-demand PR builds available to simplify dealing with that sort of circular review dependency, rather than me custom building something and tossing it on DockerHub.
PCS Postgres support is the only unreleased bit required for the deployments to successfully start. The remaining items are necessary for PCS to talk to KubeVirtBMC.
ochami discover staticneeds to be able to provide power action information and set BMC FQDNs:OpenCHAMI/ochami#47
OpenCHAMI/ochami#51
PCS needs a unreleased Postgres support and unmerged support for a mock credential store and HTTP BMCs:
OpenCHAMI/power-control#49
OpenCHAMI/power-control#50
The proper alternative to the power-control#50 hack is to either add BMC protocol to the SMD RFE schema or to add HTTPS support to KubeVirtBMC. The latter is doable, but I haven't started it yet.
I believe there are some unreleased changes in SMD also that this relies on. I didn't need to modify SMD, but did build a custom image off the tip of main sometime in 2025-08.