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 ...
If you launch the statefulset with the following key set
you can run
-k -H "Authorization: Bearer $(cat /var/run/secrets/...
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 ...
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.
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 ...
Changing logging driver form journald to json has fixed it.
I edited /etc/sysconfig/docker, and set
OPTIONS='--selinux-enabled --log-driver=json-file --signature-verification=false'
Then restarted docker on the nodes I needed:
systemctl daemon-reload && systemctl restart docker
Your interpretation is correct:
My current understanding is that a machine represents a raw physical or virtual machine; just the computational resources like cpu, memory and storage. Nodes, then, would represent a machine that is configured for using with OpenShift, that is, a machine that contains the services necessary to run pods and is managed by the ...
Define the number of replicas in the values.yaml and pass it anywhere in resources (statefulset)
Update 1: You can neither have a dynamic environment variable nor refer to the replicas field in STS. So the only way to get an updated count of STS in each pod is to redeploy with the new value of replicas in values.yaml:
According to this ...
Just to clarify if I got you right.
Do you want to have a separate service for every pod/replica in your statefulSet?
If so - this is not how K8s sees services being used. The service is used for grouping and load balancing purposes.
In your case, if you want to have 1-on-1 connection between an external client and a pod, I suggest deploying your statefulSet ...
According the documentation you're giving, you need to remove run-build from the command :
$ oc run NAME --image=<image> \
Million dollar question - are you running your fluentD as a DaemonSet? If not, there's a chance that fluentd simply isn't running on the node where some containers live.
Otherwise, my best guess is, it's missing permissions to read from all namespaces, especially since you mentioned you haven't attached a ServiceAccount to it. If you used a public FluentD ...
You'll want to be sure your spec.tls section has the following two items to tell the router you want both secure and insecure traffic allowed in the edge.
Basically, a Node is just a simple worker OpenShift (or Kubernetes) instance where OpenShift can schedule Pods.
Machine is a new API introduce by OpenShift 4 that manage dynamic instance provisioning on top of public (AWS, Azure...) or private (OpenStack, VMWare...) cloud provider.
While both Docker and jails have some similar functionality, they are built for different purposes.
The term "jail" comes from the FreeBSD distro. A lot of people will also refer to a chroot as a jail. At its core these jails virtually change the root directory for a process and its children. This means that these processes are contained (jailed) within ...
This error happens because the oc cluster up command spawns a Docker registry. The 172.30.0.0/16 IP range is probably corresponding to your Docker bridge network. As the registry will run in a container with an unpredictable IP address, you must indicate the IP range (--insecure-registry 172.30.0.0/16).
After trying many things, I came to know that I needed to expose the port of my application's container in order to let Prometheus or other deployments to know. After exposing the port, I could see my application under targets on Prometheus and I could scrape all JMX and JVM metrics. Hope this would help someone in future...
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 ...
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.
Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.
Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently named spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t an “image puller” until you explicitly ...
Yes, you can. HAProxy is purpose built to balance any TCP or HTTP connection. My old company used to run every component of Kafka with HAproxy.
Here is a whole project dedicated to running auto-scaling Kafka in Docker using HAproxy: https://github.com/pozgo/docker-kafka
You can even see their HAproxy config here where they specify the broker check (port ...