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

Configuring KEDA and CALICO with Kubesphere #6065

Open
amujeeb7492 opened this issue Mar 21, 2024 · 8 comments
Open

Configuring KEDA and CALICO with Kubesphere #6065

amujeeb7492 opened this issue Mar 21, 2024 · 8 comments
Labels
area/observability help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. question Further information is requested

Comments

@amujeeb7492
Copy link

I am trying to configure KEDA and CALICO into Kubesphere to test a scenario where horizontal autoscaling can be done through KEDA and pod ip address is assigned through CALICO.

I want to setup the below scenario through Kubesphere where I can leverage the functionalities of the below tools and can be integrated with Kubesphere.
Cluster Autoscaler
Calico
Fluentbit
KEDA
Auto deployments
Sealed secrets
Prometheus
Ingress Controller

Need inputs on this use case.

@calvinyv
Copy link
Member

/assign @kubesphere/sig-observability

@calvinyv calvinyv added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. question Further information is requested area/observability labels Mar 21, 2024
@benjaminhuo
Copy link
Member

@amujeeb7492 we've tested autoscaling with KEDA customized metrics and there's no problem found. The only problem you may need to notice is each component's compatibility with K8s

@amujeeb7492
Copy link
Author

@benjaminhuo

I can see KEDA is compatible with kubernetes 1.27 version. in kubesphere we have only 1.23 version of kubernetes and didn't find the option to upgrade it.

@calvinyv
Copy link
Member

pls double check keda official doc: https://keda.sh/docs/2.13/operate/cluster/
The latest KubeSphere 3.4.1 is compatible with K8s 1.26, which should be okay for you

@amujeeb7492
Copy link
Author

Sure @calvinyv
@benjaminhuo
Can you also confirm if Kubesphere is compatible to accommodate these below list of applications.
Cluster Autoscaler
Calico
Fluentbit
Auto deployments
Sealed secrets
Prometheus
Ingress Controller

@calvinyv
Copy link
Member

The KubeSphere comes with built-in Calico, Fluent Bit, Prometheus, and Ingress Controller. Additionally, I need to clarify that KubeSphere is not a software that operates independently of Kubernetes; it is a software stack that runs on top of Kubernetes. Therefore, all the software you mentioned, as long as it is compatible with Kubernetes, should theoretically be compatible with KubeSphere. The only potential concern is that for the software not integrated into KubeSphere, there will be no UI elements, and you would have to manage and configure them through our web kubectl command line or web yaml editor.

@amujeeb7492
Copy link
Author

@calvinyv thanks for the clarification. I can see prometheus is configured by default, By default flannel is available, I have modified to Calico, kubernetes is in built,
Is there any specific tool is available which can be replaced sealed secret(storing/retrieving sensitive data)

@calvinyv
Copy link
Member

@calvinyv thanks for the clarification. I can see prometheus is configured by default, By default flannel is available, I have modified to Calico, kubernetes is in built, Is there any specific tool is available which can be replaced sealed secret(storing/retrieving sensitive data)

I'm not sure about it, I think you need to do your own investigation and evaluation on it. For a quick search result, I see this public comparing link with SOPs: https://www.reddit.com/r/kubernetes/comments/o4xhm7/whats_the_effective_difference_between_sealed/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/observability help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants