rollout | - Fast feature flags based on Redis | Access Management library

We are a biotech company from which some users use Cytoscape. We normally "rollout" or "deploy" software silently with PDQ Deploy.

Cytoscape has been working for quite a while until I updated to 3.8.2 version. Now, I'm probably right this has something to do with Java.

Whenever I try to silently install it, I get "Error 83, no JRE found" so it aborts the install right at the start. Silent parameter: -q

Weird thing is, I tried multiple Java instances on those PC's. I tried Oracle JDK16 & OpenJDK 16 while also changing the JAVA_HOME env to their respective folder.

JRE11 doesn't exist for end users either, should be within the JDK folders but the silent install keeps throwing "No JRE found" despite both Oracle JDK and OpenJDK installed and each have their env tested.

What am I missing?

I'm trying to configure a canary rollout for a demo, but I'm having trouble getting the traffic splitting to work with linkerd. The funny part is I was able to get this working with istio and i find istio to be much more complicated then linkerd.

I have a basic go-lang service define like this:

Trying to get the icons to appear to the right of the header text. Cannot use

I've created a simple K8s deployment with the kubectl create command

I'm looking at using canary deployments in Istio but it seems it randomly distributes requests to new and old versions based on a weighting. This implies a user in the business could see one behaviour one minute and different behaviour the next minute & people within teams could experience different behaviour to each other. For this reason it seems if I want consistent behaviour for a user or team I need to build my own roll-out mechanism where I can control who moves on to the new service version.

Am I correct or am I misunderstanding how Istio canary rollout works?

We are developing a UMDF device driver that has passed the necessary HLK tests and even Windows Update on test distribution does not seem to show and errors after the update. But in the actual driver submission to Windows Update, on the Gradual Rollout phase, a large number of users have encountered CM_PROB_FAILED_POST_START (error code 43) enough to pause the driver distribution and reject it eventually.

Is there a better way of simulating/reproducing this Gradual Rollout issue safely, aside from putting the driver into Windows Update test distribution? From our checking, entries in the driver install logs (C:\Windows\Inf\setupapi.dev.log) always result SUCCESS, with return codes from each setup phase returning 0x0. EventViewer also show no signs of driver failure or warning. Are there anymore things that could be useful in finding out if Code 43 has occurred on the devices?

Any help would be much appreciated, thanks.

I have a deployment config on openshift 4, I want to lunch a number of pods via openshift API, can I lunch a new rollout of this deployment config via a curl API call, if yes how?

I want to periodically restart the deployment using k8s cronjob.

Please check what is the problem with the yaml file.

When I execute the command from the local command line, the deployment restarts normally, but it seems that the restart is not possible with cronjob. e.g $ kubectl rollout restart deployment my-ingress -n my-app

Consider an Ansible inventory with an unknown number of servers in a nodes key.

The script I'm writing should be usable with different inventories that should be as simple as possible and are out of my control, so I don't know the number of nodes ahead of time.

My command to run the playbook is pretty vanilla and I can freely change it. There could be two separate commands for both rollout stages.