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

Point to "Confluent for Kubernetes Scenario Examples" repo #1060

Open
chuck-confluent opened this issue Jan 10, 2022 · 2 comments
Open

Point to "Confluent for Kubernetes Scenario Examples" repo #1060

chuck-confluent opened this issue Jan 10, 2022 · 2 comments

Comments

@chuck-confluent
Copy link

I think a lot of folks come here to look for examples, and there is a kubernetes folder that shows a demo. That's great, but I think there should also be a link to https://github.com/confluentinc/confluent-kubernetes-examples which is a pretty comprehensive demo repo for CfK

@ybyzek
Copy link
Contributor

ybyzek commented Jan 10, 2022

@chuck-confluent agree, and even more so, perhaps https://github.com/confluentinc/examples/tree/7.0.1-post/kubernetes should be deprecated entirely because it uses older version of Confluent Operator. Would be great to get PM input on this (@amitkgupta ?)

@amitkgupta
Copy link

@ybyzek I think the demos in this repo are nice because (a) they include the Kubernetes cluster setup part too -- we have folks ask us from time to time for exactly this, the full flow on AWS or Azure starting from nothing, whereas confluent-kubernetes-examples assumes you BYOKubernetes, and (b) they have the high fidelity docs.confluent.io treatment with a more Confluent-native look and feel. We should aim to update them to use the new CFK rather than deprecating them.

@chuck-confluent thinking this through, maybe rather than linking to that other repo, the content from that repo should be merged into this one. As long as it's okay that some demos have the user walk through the actual commands the product offers without the make wrappers and some have the make wrappers, and if it's okay that some have the high-fidelity docs and some are just GitHub Markdown files, I think the two types can co-exist here nicely.

@rohit2b @arodoni wdyt?

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

3 participants