Closed ericpromislow closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/173537284
The labels on this github issue will be updated when the story is started.
Hi @ericpromislow
We've seen that eirini helm templating sets cc_internal_api
in the events section of the config map to https://{{ .Values.opi.cc_api.serviceName }}.{{ .Release.Namespace }}.svc.cluster.local:9023
.
There are couple of problems there:
cc_api.serviceName
is api
, but it should be capi
for cf-for-k8sThe easiest change is to modify that property in the config map to something like http://capi.cf-system.svc.cluster.local
which will stop the crash reporter updates failing.
In the meantime, we'll consider how to make the templating in the configmap more flexible, although note that we're dropping helm templating in the near future, just providing example deployment files and docs, in which case changing your configmap templating is the correct fix.
Separate PR dealing with permissions to access events done in https://github.com/cloudfoundry-incubator/eirini-release/pull/174
Description
We modified the catnip sample app so when we call it with ENDPOINT/sigterm/KILL the handler calls os.Exit(0). We don't see any crash events
Steps to reproduce
Made these changes in cf-for-k8s:
and in cf-acceptance-tests:
Ran
kapp deploy -a cf <(ytt -f config -f $values_file) -y
z catnip
cf push catnip
curl catnip.DOMAIN/sigterm/KILL
cf events catnip
What was expected to happen
I was expecting to see some events that contained the string
audit.apps.process.crash
What actually happened
Additional information (optional)
The catnip app without
os.Exit(1)
doesn't seem to actually exit.