I'm not altogether sure if there actually is a problem you're trying to solve, or whether you are looking for confirmation that you are on the right track. Some thoughts:
Internally openshift should be able to allocate dedicated pods
Sure. Add a post-build step in your CI pipeline which does the following:
Fashion a .yaml or .json description of that ...
AFAIK neither OpenShift nor Kubernetes itself allow you to externalize services configuration. You should have a bunch of yml/json files somewhere and control their deployment/configuration using CLI tools.
But there is Rancher which in version 2.0 allow us to import external Kubernetes clusters and manage them as Rancher's own environments.
The question hasn't had an answer in seven months so I will promote my upvoted comment to an answer:
Finding the lifecycle of a specific message across services is known as "distributed tracing". Distributed tracing requires more than just capturing logs. OpenShift uses Kubernetes which is part of cncf.io/projects which governs opentracing.io and has one ...
In my experience Openshift is open in terms of supporting good Kubernetes tools that the community comes up with. You can adopt the Kubernetes tooling that fits your needs. We use Helm to manage the configuration objects (aka yaml) of our applications running in our Openshift cluster. Helm can manages both genetic kubernetes objects as well as openshift ...
There's apparently 2 methods one can use to leverage tridentctl to interact with a running Trident Pod in their Openshift/Kubernetes cluster.
1. Server string
The tridentctl CLI can be instructed to talk to whatever server you want remotely using the -s or --server argument. In this context you could use the approach of remote shelling into the Trident Pod ...
Finnaly, I found the solution, thanks to @simbo1905.
All that I need to fix that problem:
values.yaml Child Chart 1 (or two)
In the Child Chart 2 nameOverride became to chart-2-postgres.
So it turns out the only way to edit the statefulset, and this is by design, is to delete it and recreate it with the new values.
Doing that does not delete or stop the pods or the the PVCs - those will re-attach to the new statefulset spun up later, so you won't lose anything. N.B.: you can delete the pods, and the PVCs will still ...
The simplest way is to find the icon that scales the application up and click it. In the current UI it's in Project --> Overview --> expand the application info (">" icon to the left), --> click "^" next to the blue circle to the right.
This gives you a default load-balancing across as many PODs (instances) of the application as your resources and ...