Anirudhaagrawal opened a new issue #16039:
URL: https://github.com/apache/airflow/issues/16039
**Apache Airflow version**: latest. I am using the latest apache/airflow
image from dockerhub.
**Kubernetes version**:
```
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2",
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean",
BuildDate:"2021-01-13T13:28:09Z", GoVersion:"go1.15.5", Compiler:"gc",
Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.12",
GitCommit:"e2a822d9f3c2fdb5c9bfbe64313cf9f657f0a725", GitTreeState:"clean",
BuildDate:"2020-05-06T05:09:48Z", GoVersion:"go1.12.17", Compiler:"gc",
Platform:"linux/amd64"}
```
**What happened**:
I added the following block of code to the user values in the helm chart and
because of that, the pod failed to start because the liveliness probe failed.
```
ports:
airflowUI: 80
```
```
Normal Scheduled 3m19s default-scheduler Successfully
assigned ucp/airflow-webserver-5c6dffbcd5-5crwg to
ip-abcd.ap-south-1.compute.internal
Normal Pulled 3m18s kubelet Container
image "xyz" already present on machine
Normal Created 3m18s kubelet Created
container wait-for-airflow-migrations
Normal Started 3m18s kubelet Started
container wait-for-airflow-migrations
Normal Pulled 3m6s kubelet Container
image "xyz" already present on machine
Normal Created 3m6s kubelet Created
container webserver
Normal Started 3m6s kubelet Started
container webserver
Warning Unhealthy 2m8s (x9 over 2m48s) kubelet Readiness
probe failed: Get http://100.124.0.6:80/health: dial tcp 100.124.0.6:80:
connect: connection refused
Warning Unhealthy 2m4s (x10 over 2m49s) kubelet Liveness
probe failed: Get http://100.124.0.6:80/health: dial tcp 100.124.0.6:80:
connect: connection refused
```
**What you expected to happen**:
The liveliness probe should pass.
**How to reproduce it**:
Just change the default port for airflowUI from 8080 to 80.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
