-
Notifications
You must be signed in to change notification settings - Fork 18
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
Trying to trigger on 3rd party resource creation. #11
Comments
Thanks for reporting this. This is related to the issue StackStorm/st2#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 |
Just FYI - this behavior is addressed in StackStorm/st2#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.
The text was updated successfully, but these errors were encountered: