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
I've deployed Stigatron to our cluster, but it appears that the rancher-cluster-id-finder initContainer for stigatron-heimdall2 is unable to get the cluster id from Rancher. I'm seeing the following error
Error: rancher cluster id not found
Usage:
rcidf id [flags]
Flags:
-h, --help help for id
Global Flags:
--configmap-key string key in configmap
--configmap-name string name of configmap to create
--configmap-namespace string namespace of configmap
--debug enable debug logging
--kubeconfig string path to kubeconfig file
--write-file string path to write output
rancher cluster id not found
We are running in an environment where we have to set HTTP(S)_PROXY and NO_PROXY env vars, and I've manually added those after deploying with no luck. I also manually added the --debug flag to the initContainer, but it doesn't appear to provide any additional information.
The text was updated successfully, but these errors were encountered:
@ethanchowell thanks for the ticket. Think I've identified the issue (being the mechanism we're using to find the clusterId of the downstream clusters is a race condition to the life of the cluster itself). There's a fix that I'll start working this afternoon, will keep you posted when we get it tested.
I've deployed Stigatron to our cluster, but it appears that the
rancher-cluster-id-finder
initContainer forstigatron-heimdall2
is unable to get the cluster id from Rancher. I'm seeing the following errorWe are running in an environment where we have to set
HTTP(S)_PROXY
andNO_PROXY
env vars, and I've manually added those after deploying with no luck. I also manually added the--debug
flag to the initContainer, but it doesn't appear to provide any additional information.The text was updated successfully, but these errors were encountered: