Bipin Jethwani
Bipin Jethwani
Why's there JDK inside the camel-k-kit-* images? And 384MB image for a simple route with basic log and timer components ? This is using one of your samples ``` cd...
Doc: https://camel.apache.org/camel-k/1.9.x/observability/monitoring.html As per the doc, I installed prometheus-operator. `$ kubectl apply -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/bundle.yaml` Check the error below: ``` customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com...
How to get rid of this issue while working with Camel k in KIND cluster? `failed: could not pull base image image adoptopenjdk/openjdk11:slim: Get \"https://auth.docker.io/token?scope=repository%3Aadoptopenjdk%2Fopenjdk11%3Apull&service=registry.docker.io\": dial tcp: i/o timeout` I...
Documentation here talks about enabling camel-k operator monitoring using kamel cmd util BUT it's missing information about enabling the same using camel-k helm chart. https://camel.apache.org/camel-k/1.9.x/observability/monitoring/operator.html
Why is timer to aws-s3 kamelet based routing looking for knative? I installed camel-k operator, and I see that "aws-s3-streaming-upload-sink" is ready. ``` % k get kamelet | grep s3...
``` % kubectl version --short Client Version: v1.23.1 Server Version: v1.21.1 ``` ``` % kamel version Camel K Client 1.8.1 ``` https://camel.apache.org/camel-k/1.9.x/running/running.html `kamel run hello.groovy` ``` {"level":"info","ts":1654957525.8224964,"logger":"camel-k","msg":"spectrum - 2022/06/11 14:25:25...
I enjoyed using this as krew plugin to access k8s. But I had a question if it's safe to share the client-secret as part of kubeconfig to all the dev...
I have a situation wherein I've up to 3kto 4k secrets changing in an instant. I'm using Reloader together with https://github.com/appscode/kubed. A change in one secret is synced to all...
### Report I got below config ``` apiVersion: keda.k8s.io/v1alpha1 kind: ScaledObject metadata: name: "removed" spec: scaleTargetRef: deploymentName: "removed" minReplicaCount: 0 cooldownPeriod: 30 triggers: - type: prometheus metadata: serverAddress: "removed" metricName:...
kind version kind v0.8.1 go1.14.2 darwin/amd64 ``` kind create cluster --config -