Frequently asked questions
Find answers to the most common questions we receive about Conduktor Platform.
Can't find what you're looking for? Get in touch with us
- How does Conduktor Cloud differ from the 'Self-Managed' version of Conduktor?
Conduktor Cloud offers the same capabilities, including all our solutions, scalability, and resiliency available in our self-managed software, but without having to worry about installation or cluster administration.
- What services are provided in the Conduktor Cloud?
Conduktor automatically provisions infrastructure, deploys and configures cluster software, maintains availability, provides scalability, performs backups, and handles software upgrades including Conduktor, operating system, and system software.
- Can I use Active Directory for SSO?
Yes. We support any OIDC, Active Directory, or LDAP standard identity provider. Further this does not require a connection back to Conduktor. It integrates directly with your identify provider.
- How can we deploy Conduktor Platform?
We have two distribution models; Either a docker container that you can deploy wherever you like, or a managed option (Conduktor Cloud), where we run the Platform for you and you connect it to your Kafka environment.
With the Docker container you can run Conduktor in any platform that runs Docker containers (ECS/EKS/Fargate, EC2, Kubernetes, GKE, Azure Container service, etc.).
- Does Role Based Access Contol (RBAC) in Conduktor platform apply to Kafka also?
Right now it does not. It's on our roadmap to make RBAC trickle down to Kafka ACLs also.
- Can we use IAM + MSK?
Yes! Conduktor does not currently support modifying IAM policies but is fully compatible with IAM for MSK authentication.
- Do you have a Helm chart for deploying in my Kubernetes environment?
We are working on a helm chart and will make this available soon.
- Is access to the internet required to run the Conduktor Platform?
No, you can run an air gapped docker image in your environment without internet access.
- Can we externalize Postgres & other data storage?
Yes! The instructions for doing this can be found here.
- What schema registries do you support?
Conduktor currently supports Confluent Schema Registry, as well as AWS Glue Schema registry.
- Do you have Terraform or CloudFormation?
We currently have a public cloud formation available here.
- Do you have a managed (SaaS) option? When will it have feature parity with the Docker installation?
We have fully managed SaaS as an option. You can sign up here.
Currently, Monitoring is unavailable in Conduktor Cloud. However, we expect to have parity beetween Docker and SaaS by January 2023.
- What kind of compliance requirements does your SaaS product satisfy?
None for now. However, we are working on a SOC 2 Type 2 compliance.
- What is different about Conduktor Testing from other options such as test containers and jUnit?
Conduktor testing is an end-to-end and integration testing environment. It is designed to be used by multiple teams to share knowledge and provide global visibility of test strategy throughout an organization. In addition, Conduktor Testing provides data validation and data checks at each step of a distributed system. This ensures both data correctness and application resilience.
- What is the suggested settings for running the docker image?
We suggest you add a docker volume. If you fail to add the second --mount option each time you restart the docker container your settings and metrics will be erased. See our Docker Quick Start guide for exact commands.
- I want to run this docker image in AWS Fargate/ECS/EKS, how can I do that?
We are working on a manifest as well as helm chart to enable this. For now, deploying Conduktor platform as a single container works for most folks. https://docs.docker.com/get-started/kube-deploy/ has instructions.
- What are the suggested resources that should be dedicated to Conduktor Platform?
We are working on a Helm chart to enable this. For now, deploying Conduktor platform as a single container works for most folks. See https://docs.docker.com/get-started/kube-deploy/ for more instructions.
- If I have licenses of Conduktor Desktop is it still account.conduktor.io where I manage these licenses, add/remove etc?
Yes, if you have licenses of Conduktor Desktop you manage them via account.conduktor.io. Please see more information on account management for Conduktor Desktop here. If you are using Conduktor Platform you will manage the users of your subscription from the Admin section of your deployment, whether using Conduktor Cloud or our docker image on your environment. Please see a working example on our live demonstration here
- Does the Data Masking solution make any changes to my Kafka data?
No it does not. The data is masked on the Conduktor Platform only.
- If I am currently using JMX exporter on a specific port, how do I utilize Conduktor Platforms Monitoring features? Do I have to use a specific port?
You can use the port you are currently using, just change the configuration called jmxScrapePort as shown here.
- What other integrations are planned for Monitoring and Alerting? For example, MS Teams, Email?
We plan to have webhooks available so you can integrate with other services.
- How are the cluster credentials I enter on the platform stored?
They are secrets that are encrypted to/from the DB (via AES encryption algorithm), of which the key is accessible only via our internal DevOps team.
- Are the timestamps in Conduktor Console for Kafka messages based on Local time or Coordinated Universal Time(UTC)?
The timestamps of Kafka messages on Conduktor Console are based on the local time zone of the user. Our team are working on functionailty to allow users be able to choose between either local time and UTC on Conduktor Console.