-
Notifications
You must be signed in to change notification settings - Fork 2
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
Alloy v2 #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine. My biggest comment/desire for change is coming up with something better than just repeated kubectl get pods
to validate that the controllers were deployed properly.
@@ -26,3 +26,15 @@ Consume an event as conditionorc | |||
``` | |||
nats consumer sub --creds=/root/nsc/nkeys/creds/KO/controllers/conditionorc.creds -s nats://nats:4222 | |||
``` | |||
|
|||
|
|||
list keys in statusKV buckets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably more useful to get the keys and examine individual data with kv get --raw
Implement support to run Alloy as a controller on the JS
depends on