Minor changes to quickstart YAML for AKS Automatic policy.

[owainow]

Purpose

Changes made to aks-store-ingress-quickstart.yaml to enable deployment in accordance with the AKS Automatic Getting Started guide. Due to AKS Automatic Policy the current quickstart is not able to be deployed and is blocked at point of admission due to:

• Images being tagged with latest as opposed to pinned versions.
• No Readiness or Liveness probes for RabbitMQ.

As a result:

• I have pinned the store image versions to latest image digest.
• Pinned busybox version to 1:35
• Added liveness and readiness probes for RabbitMQ.

I did debate creating a seperate file for automatic and have the docs changed in https://learn.microsoft.com/en-us/azure/aks/automatic/quick-automatic-managed-network?pivots=azure-portal to allow for this file to continue using latest tags but in reality this would then mean going forward their would be a fairly useless duplication of effort imo.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[X] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Follow the quickstart https://learn.microsoft.com/en-us/azure/aks/automatic/quick-automatic-managed-network?pivots=azure-portal and observe policy blocks. Apply the updated file to automatic cluster and observe admission and working applications.

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information