Comments (1)
When we deploy Siddhi operator without NATS which would be totally fine when we deploy stateless Siddhi apps, then it prints an error like below saying unable to find NATS.
"msg":"if kind is a CRD, it should be installed before calling Start","kind":"NatsCluster.nats.io","error":"no matches for kind \"NatsCluster\" in version \"nats.io/v1alpha2\""
"msg":"if kind is a CRD, it should be installed before calling Start","kind":"NatsStreamingCluster.streaming.nats.io","error":"no matches for kind \"NatsStreamingCluster\" in version \"streaming.nats.io/v1alpha1\""
After this error, if we deploy NATS and NATS streaming operators and then tries to deploy a stateful distributed Siddhi app, the operator gives the following error.
{"level":"error","ts":1564141174.2775638,"logger":"siddhi","msg":"no matches for kind \"NatsCluster\" in version \"nats.io/v1alpha2\"","Request.Namespace":"default","Request.Name":"power-consume-app","error":"no matches for kind \"NatsCluster\" in version \"nats.io/v1alpha2\"","stacktrace":"github.com/siddhi-io/siddhi-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error
src/github.com/siddhi-io/siddhi-operator/vendor/github.com/go-logr/zapr/zapr.go:128
github.com/siddhi-io/siddhi-operator/pkg/controller/siddhiprocess.(*ReconcileSiddhiProcess).updateErrorStatus
src/github.com/siddhi-io/siddhi-operator/pkg/controller/siddhiprocess/operator.go:195
github.com/siddhi-io/siddhi-operator/pkg/controller/siddhiprocess.(*ReconcileSiddhiProcess).Reconcile
src/github.com/siddhi-io/siddhi-operator/pkg/controller/siddhiprocess/siddhiprocess_controller.go:186
github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
src/github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215
github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1
src/github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158
github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
src/github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil
src/github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait.Until
src/github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}
At that time I have to do as follow for a successful distributed Siddhi app deployment.
- Remove Siddhi Operator
- Install NATS and NATS streaming operator
- Redeploy the Siddhi Operator
from siddhi-operator.
Related Issues (20)
- There is no way to view the partial apps after a distributed deployment HOT 1
- Missing the Readiness and Liveness probes after deployment update
- [Doc] Create a doc about how to deploy Siddhi apps in openshift using Siddhi operator
- Disable automatic ingress creation not working
- Use K8s stateful set instead of deployment for stateful Siddhi runner deployments
- Have a consistent way to handle HTTP traffic in distributed deployment
- Need to have common build script for operator build and create artifacts
- Adding resource limits for the deployments
- Test Siddhi against NATS Operator v0.6.0
- Find out the usage of K8s job for Siddhi parser
- No artefacts for 0.2.2-RC2 HOT 1
- Fix NATS-Streaming Operator version in docs HOT 1
- Print error log when automatic NATS creation fails in the non-distributed mode of Siddhi operator
- Duplicate cms when yaml file is edited and pod restarted in k8s
- Security Issues in siddhi operator Image due to older golang versions. HOT 13
- Issue in building image from source HOT 1
- Unable to deploy custom Siddhi Apps on a Kubernetes cluster as documented HOT 2
- Stateful Siddhi Application fails deployment if persistence volume is unavailable
- Support for mounting volume mounts to Siddhi instance
- Events are potential to loss when NATS becomes unavailable in the Distributed mode HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from siddhi-operator.