Open jeremyjjbrown opened 7 years ago
Thanks for reporting this.
This is related to the issue https://github.com/StackStorm/st2/issues/3385.
@Kami is right that part of the problem is st2/#3385, where validation is also enabled.
The problem also seems to be related to this template https://github.com/StackStorm-Exchange/stackstorm-kubernetes/blob/master/etc/st2packgen/templates/sensor_template.yaml.jinja#L13
payload_schema:
type: "object"
properties:
resource:
type: "obj"
name:
type: "obj"
labels:
type: "obj"
object_kind:
type: "obj"
namespace:
type: "obj"
Rather than type: "obj"
, it probably needs to be type: "object"
. May need a uid
object in there too.
Just FYI - this behavior is addressed in https://github.com/StackStorm/st2/pull/3390 and will be included in the next release. Still, the schema should be adjusted to match the trigger payload anyways in the meantime.
I've created branch 1.5 from the latest 1.5.x kubernetes swagger.json
We're currently testing this on our dev cluster - if it looks good I'll merge tonight/tomorrow
I created a Kubernetes 3rd party resource api and I'd like to trigger a rule. However I am not getting any trigger instances in my ST2 and it appears most K8s events are failing validation.
/var/log/st2/st2sensorcontainer.log is full of log info from the K8s API server with many instances of
Not sure what the issue is here.