Skip to content
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

streaming ops documentation to deploy in our kubernetes cluster to connect to confluent cloud subscription we already have #89

Open
chinnasamyb opened this issue Jul 2, 2021 · 3 comments

Comments

@chinnasamyb
Copy link

Is there a documentation on how to deploy this stream ops in our kubernetes cluster to connect to our existing confluent cloud subscription?

I cloned this repo and built the docker image, deployed my kubernetes cluster. when I added a topic configuration the streaming operator detects the config , it tries to connect to confluent cloud and it error out because I haven't configured the confluent cloud broker or api keys to connect to my confluent cloud subscription. I see a reference to XX_CCLOUD_EMAIL=[email protected] and XX_CCLOUD_PASSWORD=YYYYYYYYYY in the git repo. But I do not see that addedd to the image (https://github.com/confluentinc/streaming-ops/tree/main/images/ccloud-operator/Dockerfile).

I want to use this operator to create and manage topics decoratively

@chinnasamyb
Copy link
Author

@chinnasamyb
Copy link
Author

I am able to follow the document to create sealed secrets and deployed the sealed secret. We have single sign on setup for user accounts in confluent cloud. So when I specify the user name and password CCLOUD_EMAIL= and CCLOUD_PASSWORD=. in the sealed secret, it says invalid email or password. Could you please let me know how to handle CCLOUD_EMAIL and CCLOUD_PASSWORD for SSO enabled confluent cluster?

@ybyzek
Copy link
Contributor

ybyzek commented Jul 7, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants