Comments (7)
Thanks, that works. I had wrapped the licence JSON in square brackets, like LENSES_ZOOKEEPER_HOSTS. Removing the brackets as you've shown for LICENSE above fixed it. Seems an inconsistency more than a bug, I guess?
from lenses-docker.
@grrywlsn can you try the Helm chart? We recommend using it.
from lenses-docker.
@grrywlsn I am assuming that you have i) received a license file and ii) you are mounting the license file into the docker with the -v
parameter
Also can join our Slack channel @ https://launchpass.com/landoop-community so we can better assist you in real-time ?
from lenses-docker.
I do have a valid licence file, but it didn't get picked up as an environment variable.
I've got the deployment to work by passing it in as a ConfigMap to appear as a file at /mnt/secrets/license.json but that's less ideal; an environment variable (which the docs suggest should work) would be cleaner imo.
from lenses-docker.
Hmm, this is funny because we do use this functionality internally as well —alas not in kubernetes—, so I consider it well tested.
Let me do some tests on k8s and come back to you.
from lenses-docker.
Hi @grrywlsn. I can't reproduce it locally, so I need some help.
Below you'll find an example of how I added the license and other secrets in my kubernetes yaml description. The example below should work if you replace your cluster's addresses and license.
A possible cause for the issue, is that the license is in json format, which can be interpreted as part of the yaml rather than just a value. Please notice how in my example I set the license value to be interpreted as a literal:
- name: LICENSE
value: |
{"source":"Landoop LTD","clientId":"andmarios","details":"Lenses","key":"a-very-big-string"}
The configuration I just tested:
apiVersion: v1
kind: Pod
metadata:
name: lenses
labels:
name: lenses
spec:
containers:
- name: lenses-runtime
image: landoop/lenses:latest
ports:
- containerPort: 9991
env:
- name: LENSES_PORT
value: "9991"
- name: LENSES_JMX_PORT
value: "9015"
- name: LENSES_KAFKA_BROKERS
value: PLAINTEXT://kafka:9092
- name: LENSES_ZOOKEEPER_HOSTS
value: |
[
{url: "kafka:2181", jmx: "kafka:9585"}
]
- name: LENSES_SCHEMA_REGISTRY_URLS
value: |
[
{url: "http://kafka:8081", jmx: "kafka:9582"}
]
- name: LENSES_CONNECT_CLUSTERS
value: |
[
{
name: "dev",
urls: [
{url: "http://kafka:8083", jmx: "kafka:9584"}
],
statuses: "connect-statuses",
configs: "connect-configs",
offsets: "connect-offsets"
}
]
- name: LENSES_SECURITY_MODE
value: BASIC
- name: LENSES_HEAP_OPTS
value: "-Xmx1G"
- name: LENSES_SECURITY_USERS
value: |
[
{"username": "admin", "password": "admin", "displayname": "Lenses Admin", "groups": ["adminGroup"]},
{"username": "read", "password": "read", "displayname": "Read Only", "groups": ["readGroup"]}
]
- name: LENSES_SECURITY_GROUPS
value: |
[
{"name": "adminGroup", "roles": ["admin", "write", "read"]},
{"name": "readGroup", "roles": ["read"]}
]
- name: LICENSE
value: |
{"source":"Landoop LTD","clientId":"andmarios","details":"Lenses","key":"a-very-big-string"}
from lenses-docker.
Is the above ^ helping @grrywlsn ?
from lenses-docker.
Related Issues (19)
- Failed to create symbolic link '/var/www/config/run' on container restart HOT 1
- Avien docker image Failed to open the storage [lensesdb] HOT 2
- Require checksum check in dockerfile
- Lenses behind reverse-proxy HOT 5
- For large truststore files, the container fails to start
- Minikube lenses example bundled in the repo doesn't work
- Topic data grid does not follow window width changes
- kafka connect JMX connection issue
- [Redis-Sink] No writers set for connect.redis.kcql HOT 1
- kafka connect not showing on topology
- unable to establishes connection to postgressql database
- Error on starting container: [dumb-init] -e: No such file or directory
- Connector config editor gives false impression that lines can be continued with \
- ERROR! Lenses port (LENSES_PORT=9991) is in use by some other program. HOT 4
- ssl.endpoint.identification.algorithm not working HOT 1
- Inconsistent icon and text alignment in sidebar
- Cannot create connectors for connect cluster named “connect” HOT 1
- Can't connect to default Influxdb v1.6.2, connection refused 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 lenses-docker.