[Kibana] Closes #1574 Fix readinessProbe double brace notation error

[Gaian-pixel]

The error was caused by an incorrect double brace notation inside the last readinessProbe condition, causing the condition to never be true
Fixed by removing a couple of braces.

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[cla-checker-service]

💚 CLA has been signed

[Gaian-pixel]

x Author of the following commits did not sign a Contributor Agreement: f5bdae6

Please, read and sign the above mentioned agreement if you want to contribute to this project

signed

[jmlrt]

Hi @Gaian-pixel, the double bracket is the correct syntax in bash. Can you provide more details about the error you are trying to fix?

[Gaian-pixel]

Hi @Gaian-pixel, the double bracket is the correct syntax in bash. Can you provide more details about the error you are trying to fix?

But it is actually using sh

Here is where it is declared

{{ toYaml .Values.readinessProbe | indent 10 }}
          exec:
            command:
              - sh
              - -c 

[jmlrt]

Yes, it was using sh in the previous versions but it has already been fixed in #1530 by changing the shell to bash.

[Gaian-pixel]

Yes, it was using sh in the previous versions but it has already been fixed in #1530 by changing the shell to bash.

OK I was not aware of the fix.
Thanks for the reply.