You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# calicoctl get nodes
NAME
# calicoctl get hostendpoints
NAME
Running the container with the -startup parameter seems to register the host as a node, but it is not added as a hostendpoint (which I think is expected), but it also initializes the default IPAM
Context
I am running a POC to set up calico as a FW management on VM/Baremetal server outside the K8s clusters we have in place
Your Environment
Calico version: v3.27.2
Orchestrator version (e.g. kubernetes, mesos, rkt): No oschestrator in place, things are running on virtual machines
Operating System and version: Oracle Linux 9.3
The text was updated successfully, but these errors were encountered:
The doc just looks wrong to me; it runs calico-node -felix which will run only felix, not the startup scripts that would initialise the datastore as it suggests.
Expected Behavior
Configuring calico-node on non cluster hosts should register the host endpoints into ETCD and on the Calico Cluster.
Current Behavior
Running calico-node does not add the host endpoints, not properly setting things up.
Possible Solution
Looks like the documentation is incorrect/missing some steps to set things up.
Steps to Reproduce (for bugs)
Running the container with the
-startup
parameter seems to register the host as a node, but it is not added as a hostendpoint (which I think is expected), but it also initializes the default IPAMContext
I am running a POC to set up calico as a FW management on VM/Baremetal server outside the K8s clusters we have in place
Your Environment
The text was updated successfully, but these errors were encountered: