search

kubernetes-sigs / kubespray

Deploy a Production Ready Kubernetes Cluster
Apache License 2.0
16.2k stars 6.48k forks source link

Possibility to install cluster without CNI #11264

Closed ehsan310 closed 2 weeks ago

ehsan310 commented 5 months ago

What would you like to be added

I would like to install and push cluster without a default CNI and not using Kubespray to install the CNI plugin. I have tried to use cni-plugins but that will not help in case I want to install CNI like Calico which manages dynamic IPAM. The reason for cni-plugins not working was during cluster initialization there is --pod-cidr which I don't want to pass any static ip range

Why is this needed

To be able to install custom cni or another way of installing the CNI like operator based installation for Calico

yankay commented 5 months ago

HI @ehsan310

I'm not very sure, using kube_network_plugin: cni may solution the issue :-)

poblahblahblah commented 5 months ago

We do the same thing since we have another mechanism to handle CNI management outside of kubespray.

To do this we set kube_network_plugin: cni as @yankay suggested.

ehsan310 commented 5 months ago

Ok! I thought of trying this but was afraid of —pod-cidr flag actually that is only ignored when calico is chosen as CNI Maybe not really a problem!? Will try it on my lab.

do you think it is safe to change it on a running cluster?

yankay commented 5 months ago

Ok! I thought of trying this but was afraid of —pod-cidr flag actually that is only ignored when calico is chosen as CNI Maybe not really a problem!? Will try it on my lab.

do you think it is safe to change it on a running cluster?

Changing the CNI is not a safe action on a running cluster :-)

ehsan310 commented 5 months ago

In case i change cni plugin from calico to cni , do kubespray remove anything?

i have checked cni role and as far as I understood it just create folders unless some other thing is changed somewhere else.

i have to change my running cluster to calico operator based installation .

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 2 weeks ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/kubespray/issues/11264#issuecomment-2464422580): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.