What Happened?

when running minikube in github action I noticed in Ubuntu it polutes the output which is not pretty
but in github action on macOS it is doing the right thing

example can be found here

https://github.com/medyagh/test-minikube-example/runs/4613732249?check_suite_focus=true

Attach the log file

on linux

Run medyagh/setup-minikube@latest
/usr/bin/chmod +x /ho

Use case:
Add the ability to search for an element in an array and retrieve back the array index.
As per the PostgreSQL documentation:

array_position ( anycompatiblearray, anycompatible [, integer ] ) → integer

Returns the subscript of the first occurrence of the second argument in the array, or NULL if it's not present

Problem

I would like to be able to have different names for my node to help with discovery in tools like k9s.

If I (a) create the cluster and then (b) create the nodes I can achieve this.

But if I need to create the cluster and nodes at the same time i.e. via -agents flag then this is not possible.
And some use cases e.g. per-node volumes are only possible using this approach

I'm trying out running Polaris in GitHub Actions following the doc below and am finding that it is building the go binary in each workflow run.

https://polaris.docs.fairwinds.com/infrastructure-as-code/#running-in-a-ci-pipeline

Could we instead just pull the quay.io/fairwinds/polaris docker image and run the audit step inside that?

We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.

I can see where this would be a hassle on many cases, But it would be nice for new projects.

I suppose it could be a global config item that could be overridden at the individual action level:

For

Hello community,

Some context

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
• Where do you run it - cloud or metal? Kubernetes or OpenShift? OVH Managed Kubernetes
• Are you running Postgres Operator in production? no
• Type of issue? feature request

Issue

When retrieving the Custom Resource pg with the comman

we discovered, that the ITL for VMware-Checks is missing one update to the open-vm-tools argument, when trying to use this in our service definitions.

The ITL seems to be missing one update for the VMware CheckCommands using the check_vmware_esx.
This one refererences the check_vmware_esx by BaldMansMojo (https://github.com/BaldMansMojo/check_vmware_esx)

Taking a look to the code shows, tha

Users that download the windows EXE will be prompted (by browser and OS) that it is not safe because the EXE isn't signed.

There is a GitHub Action for signing: https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate

This would provide additional confidence for