search

projectcalico / calico

Cloud native networking and network security
https://docs.tigera.io/calico/latest/about/
Apache License 2.0
5.97k stars 1.33k forks source link

Helm "include calicoctl pod" boolean #6886

Closed jcpunk closed 2 years ago

jcpunk commented 2 years ago

Expected Behavior

When installing calico via helm, it would be handy if I could "flip a bit" to include calicoctl as a Kubernetes pod. This would provide a clean way to bundle up a known calicoctl within the cluster and make getting started easier.

Current Behavior

After installing the helm chart, I've got to go fetch calicoctl.

Possible Solution

Add a boolean to values.yml that will load the "calicoctl as a Kubernetes pod" workflow

Steps to Reproduce (for bugs)

  1. Install helm chart
  2. notice a lack of calicoctl

Context

I'm trying to make it easier to get up and running from scratch with the calico operators

Your Environment

caseydavenport commented 2 years ago

We want to move away from bundling calicoctl as a pod. There is a Calico API server that performs the same function as calicoctl as a pod and is the recommended way to interact with Calico APIs, and is installed by default when using the helm chart already.

What is your use-case for installing calicoctl on the cluster?

jcpunk commented 2 years ago

Mostly for looking at the IPAM. I can live with my current workflow.