Helm dependency update when upgrading chart - redis

I've recently written a Helm chart for my application adding a redis dependency in the requirements.yaml file:
dependencies:
- name: "redis"
version: "~4.0.0"
repository: "https://kubernetes-charts.storage.googleapis.com/"
I've noticed that whenever I run my helm upgrade command the redis dependency gets always reinstalled, bringing redis down all the times I just need to upgrade my application.
The command I'm running is something along the lines of helm upgrade --wait release-name ./helm-folder
Is this behaviour expected? Isn't helm supposed to only update the application pod if there hasn't been any change to the requirements.yaml/requirements.lock file?
Thanks,

We saw similar behaviour - taking out the tilde locked it down. The tilde seems to mean 'this version or greater'.

Related

testContainers and Rancher

I have a Spring Boot application with integration tests that are using testContainers.
Till recently, I used Docker Desktop and was able to easily run the test from within Intellij or from CLI.
Recently I changed my Windows machine to Rancher desktop.
Now when trying to run the integration tests gradle integrationTest I'm getting this error:
Caused by: java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration
at org.testcontainers.dockerclient.DockerClientProviderStrategy.getFirstValidStrategy(DockerClientProviderStrategy.java:109)
at org.testcontainers.DockerClientFactory.getOrInitializeStrategy(DockerClientFactory.java:136)
at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:178)
at org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
at org.testcontainers.LazyDockerClient.authConfig(LazyDockerClient.java:12)
at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:310)
Is there an additional configuration that is needed in Intellij or Rancher or Windows to make it work?
UPDATE Feb 2022: As reported here TestContainers works nicely with Rancher Desktop 1.0.1.
Based on the following two closed issues - first, second - in the testcontainers-java github, Testcontainers doesn't seem to support Rancher Desktop, at least officially.
I'm running rancher desktop version 1.0.0 on my windows mashine and could get testcontainers to work just by simple adding 'checks.disable=true' in .testcontainers.properties (located under C:\Users<your user>)
updating Rancher Desktop to version 1.0.1 fixed this issue for me
I got this error because my Rancher was using containerd. If you also use Rancher Desktop try to switch to dockerd under settings, but first back up the data you have just in case.

Up-to-date Ignite web console docker image

I'm wondering if there is a up-to-date docker image for the Ignite web console?
When I pull "docker pull apacheignite/web-console-standalone" I only get an outdated version that isn't compatible with current web agent.
Or is the Dockerfile available so I can build the image myself without starting from the ground?
Maybe there is even a Dockerfile that puts webagent and console in one?
Thanks for any help!
#dontequila.
apacheignite/web-console-standalone will be updated soon.
You can also build docker by yourself:
Checkout Apache Ignite master: Ignite Git: https://git-wip-us.apache.org/repos/asf/ignite
cd modules/web-console/docker/standalone/
./build.sh (you may need sudo).

Docker with an Apache is restarting in a loop

I have a Ubuntu 14.04 which run an app supported by Docker (version 17.05.0-ce, build 89658be) and docker-compose (version 1.16.1, build 6d1ac21). One of this dockers contains an Apache which is restating in a loop.
Is there a way to fix this without losing dockers customizations?
I re-created all dockers with
docker-compose up --force-recreate
I didn't lose anything and everything is working now.

Apache version 2.2 and security vulnerabilities

A penetration test has recently identified that one of our RHEL(6.7) servers running Apache 2.2.15 is vulnerable on a number of points and needs to be updated to the latest version 2.4. I have run yum update and it says that there are no packages marked for update. I understand that I will need to download the updates manually. There are a few questions I have around the requirement to upgrade Apache.
I am up to date on the 2.2 version tree. Does this mean that any security patches made to version 2.4 will be back patched to version 2.2.X as well?
I am running PHP (version 5.3.3) and MySQL (version 5.1.73) - will these be affected by upgrading the Apache version (Google tells me that there is no problem on both fronts - but I thought I'd ask before I started down this route).
If you experts tell me that I have no other choice but to upgrade, then I'm planning on using the instruction set here: https://unix.stackexchange.com/questions/138899/centos-install-using-yum-apache-2-4
Thank you in advance for your advice.
You could download the 2.4 source code from the Apache site and compile it. There's a setting which will configure for RedHat:
--enable-layout=RedHat
This setting will configure the paths for executables, configuration files, libraries etc in one go.
The following should be a reasonable starting point for a configuration line:
sh ./configure --enable-layout=RedHat --enable-mods-shared=all
then perform a make and make install
Do the same with a newer version of PHP (5.3.29 is available in the "old downloads" section, but try a newer version. Check the changes first though) and your problems should be lessened. Finally, MySQL or MariaDB is available for download and compilation too
Obviously, try all of this on a test machine first and back everything up. Your test machine should be as close as possible to your production machine. If you use something like VirtualBox to try it, you can take a snapshot at each point of the process and rollback if something goes wrong

Configure Redis Cluster in Ubuntu Server 14.04

I've installed redis-server using apt-get install redis-server and everything went fine.
Right now I'm trying to configure it in a Cluster mode. The problem is that in the tutorial supplied here http://redis.io/topics/cluster-tutorial they use a script called redis-trib.rb which I can't find it in my system.
Can you please tell me how can I configure my Redis to run in Cluster mode without that script ?
I would like to have a setup with two masters, each on a different machine.
Thank you very much.
Had same problem with reredis-trib.rb
This tutorial explains how to create Redis Cluster using only Redis commands: Configuring and Running Redis Cluster on Linux
You need Redis 3.0.0 beta to run Cluster. You'll not find it in a Linux distribution, since they all have copy of the stable server (fortunately!). Redis 3.0.0 will go out as a stable release the next week. You can find the source code of the stable release here: http://redis.io/download.
There is now a tutorial for Ubuntu at https://www.digitalocean.com/community/tutorials/how-to-configure-a-redis-cluster-on-ubuntu-14-04 which includes installation of a PPA to supply 3.0.x. This tutorial is only for two nodes and does not reference redis-trib.rb ...