ES-config | flexible tool for configuring multiple emulators

I'm trying to create a PostgreSQL database in a Kubernetes cluster on Digital Ocean. To do so, I've created a StatefulSet and a Service. And to set up a volume in order to persist data, I took a look at the Add Block Storage Volumes tutorial. My k8s configurations for the StatefulSet and Service are down below.

I simply used a volumeClaimTemplates . The storage class do-block-storage exists in the cluster (volumeBindingMode is set as Immediate). The pv and the pvc are successfully created.

A volumeClaimTemplates that is responsible for locating the block storage volume by name csi-pvc. If a volume by that name does not exist, one will be created.

But my pod falls in a CrashLoopBackOff. I'm getting:0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. Back-off restarting failed container

It is also worth saying that my cluster only has one node.

Can any please help me understand why? Thanks

I have a question regarding Kubernetes Liveness/Readiness probes configuration.

I have an application developed in netCore 3.1 that at this moment, in production env (version 1.0.0), doesn't have configured health checks. I have implemented the health endpoints in the second release (version 2.0.0) but how can I manage the Kubernetes deployment template file in order to be compliant with version v1 that does not have an endpoint?

If I will deploy my template with probes configured, all container that runs on v1 will fail cause no endpoint are reachable. I would like to understand if I can maintain one deployment yml file that will be compatible with v1 (without health) and v2 (with health).

Here I post an example of my actual deployment yml:

According to the official resource, logging configuration relies on application.properties file.

Now I need to have several configuration according to the cluster in use (let's say we have the typical dev, staging and production environments, thus dev should have a DEBUG level and production at least INFO).

At first I thought using Kubernetes ConfigMaps, but I can't see any connection with quarkus logging.

How can I solve this issue?

EDIT:

This is my ConfigMap

I have an ongoing requirement to patch my nginx-ingress daemonset each time I wish to expose new TCP ports. I have reviewed the documentation and I cannot understand the correct kubectl patch syntax to perform the patch. An excerpt from the yaml follows:

Environment:

• Jboss 7.2
• Java 11
• JSF 2.3
• Primefaces 10
• Primefaces theme Avalon 3.0.0

New versión of theme Avalon 3.0.0 seems that it miss class AvalonMenuRenderer on avalon-theme-3.0.0.jar.There is only META-INF folder

Could it be?

On loading the project migrated to avalon 3.0.0 I got this error.

Error log

In a multi-container pod:

step-1: Deploy first container Postgres Database and create a schema

step-2: Wait until the Postgres pod came up

step-3: then start deploying second container keycloak

I have written below deployment file to run :

I wanted to see if I can connect Spring Cloud Stream Kafka with the help of docker-compose in Docker containers, but I'm stuck and I didn't find a solution yet, please help me.

I'm working from Spring Microservices In Action; I didn't find any help by now.

Docker-compose with Kafka and Zookeeper:

I created an app using Spring Boot, JSF + Primefaces. I deployed it to Amazon Elastic Beanstalk, and set the environment variables that project needed to use.

When I tried to access my website, I got this error message:

I'm modernizing a JSF web application I took over from someone who retired and is not available for questions.

Current job is to simplify a h:dataTable. Each record has a commandLink to go to the corresponding details page.

Old version: action method openDetail(), determined the selected record by binding of the dataTable and looping trough the records to get the row.

New version: action method is now openDetail(Long id) and of course I added the parameter to the command link as well.

My action method is called with the correct parameter, I verified this by adding some log output. But the navigation-rule is not effective anymore. Although the action method returns the correct outcome, it stays on the page with the table.

The navigation-rule in faces-config.xml looks like this: