Adding Gateway Specific configuration for readinessProbe if changed to o service foo which is pre-installed via bundles.
Benefits
By Default, Gateway readinessProbe points to /opt/docker/rc.d/diagnostic/health_check.sh , which ckecks container health not Gateway
updating readinessProbe to service foo will be able to check when Gateway is ready to accept the traffic
Drawbacks
Gateway takes more than 40 sec(initialDelaySeconds) to be ready to accept traffic , which means readinessProbe check might fail few times before it gets first success
Applicable issues
fixes #
Additional information
Checklist
[] Chart version bumped in Chart.yaml according to semver.
[] Variables are documented in the README.md
[] Title of the PR starts with chart name (e.g. [charts/gateway])
[] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
…
Description of the change
Adding Gateway Specific configuration for readinessProbe if changed to o service foo which is pre-installed via bundles.
Benefits By Default, Gateway readinessProbe points to /opt/docker/rc.d/diagnostic/health_check.sh , which ckecks container health not Gateway
updating readinessProbe to service foo will be able to check when Gateway is ready to accept the traffic
Drawbacks
Gateway takes more than 40 sec(initialDelaySeconds) to be ready to accept traffic , which means readinessProbe check might fail few times before it gets first success
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver.[charts/gateway]
)values-production.yaml
apart fromvalues.yaml
, ensure that you implement the changes in both files