-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
container apps - support for additional settings in container apps probes #27551
container apps - support for additional settings in container apps probes #27551
Conversation
… startup_probe and readiness_probe hashicorp#25457
Type: pluginsdk.TypeInt, | ||
Optional: true, | ||
Default: 1, | ||
ValidateFunc: validation.IntBetween(1, 1), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be set to anything other than 1?
Type: pluginsdk.TypeInt, | ||
Optional: true, | ||
Default: 1, | ||
ValidateFunc: validation.IntBetween(1, 1), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Likewise here, is there a point in exposing this if it's default is 1
and can only be set to 1
anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we please remove this then (from the Computed schemas as well)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed where I added it. But kept it in ContainerAppReadinessProbeSchema to not create a breaking change
ce30625
to
c8002c0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @SpartakusMd, I've kicked off the tests. Would you mind updating the documentation with these changes as well?
@stephybun I have added the docs. Is there anything else? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests look good, thanks @SpartakusMd LGTM 👍
Thank you @stephybun for the time spent! |
InitialDelaySeconds: pointer.To(input.InitialDelay), | ||
PeriodSeconds: pointer.To(input.Interval), | ||
TimeoutSeconds: pointer.To(input.Timeout), | ||
FailureThreshold: pointer.To(input.FailureThreshold), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how come there is no success threshold property here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a container app that is failing because I can not set a success_count_threshold to it, it will assign it an empty value.
Since I have a container app that is a public container that accepts ingress, Azure does a health check of the service using startup probe.
Since I can not configure it via terraform, my container always fails until I manually configure it on the UI to have a success threshold count to be 1, which then works fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
according to the issue you are responding too: #25457
startup_probe should also have a success threshold.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was added initialy, but removed later in the same PR due to review in c8002c0
It was removed due to the fact that only a single value is accepted and that is 1
. You cannot set the value to anything else. I also use this code for our infra and it's working as expected.
The question would be how it worked until now as the option wasn't present there? If it's really needed, I guess you could create a PR with the changes from that commit to add the success threshold property and see if it's merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could create a new PR with changes from c8002c0 and put the screenshot as an explanation. Are you sure it fails due to the value being empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I am sure - because once I edit the container config on the UI, once I add a success threshold, then the container lives, otherwise it just dies and keeps restarting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I attempted to make a PR however I get denied
remote: Permission to hashicorp/terraform-provider-azurerm.git denied to Dmitriyx
I will check what the rules are for making a PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to fork the repo and make changes in the forked repository. Afterwards you can create a PR in Github.
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Community Note
Description
The available settings for the configuration of the liveness, readiness and startup probes in Azure Container Apps are lacking a few details.
FYI, There are some defaults for existing probe settings which are different between Azure and Terraform, I left them intact.
PR Checklist
Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_container_app
- added missing settings in liveness_probe, startup_probe and readiness_probe [Support for additional settings in liveness_probe, startup_probe and readiness_probe #25457]This is a (please select all that apply):
Related Issue(s)
Fixes #25457, fixes #24845