Azure / Azure/draft

Introduction of "startupProbe" to the draft templates are pods to crashloopbackoff.

Open
#485 0 comments 0 reactions 2 assignees Claimed by @bosesuneha View on GitHub
Dominant language
Go
Stars
644
Forks
74
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
We recently ran into an issue deploying contoso air onto an AKS cluster via the new draft templates. The startupprobe was causing a crashloopbackoff . We believe this is because the failurethreshold was set to 1 as well as misconfigured timeoutseconds and potentially periodseconds.

![Image](https://github.com/user-attachments/assets/f08d7cfe-763c-477b-9663-2deefe7473c8)

**Expected behavior**
Apps that use our templates should be able to come online and not run into a crashloopbackoff due to startupprobe failures.

**Screenshots**

![Image](https://github.com/user-attachments/assets/c3b8bf18-82ae-4f12-8272-1dd1cc0c07dd)

Bumping the startupprobe values caused the app to come online.
![Image](https://github.com/user-attachments/assets/f9959da5-d36e-4fc2-84e0-2787754d19bd)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.