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
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
When running the aws-installer for a 4.4 release, the etcd operator will fail to initialize a cluster if the etcdcluster CR is created asynchronously along with the etcd operator deployment. If a pause is added between the creation of the etcd operator and the etcdcluster CR, the problem goes away.
Investigate why this is an issue and update code appropriately #120
The text was updated successfully, but these errors were encountered:
This seems to be an issue with etcd operator (coreos/etcd-operator#2163). For now, we are creating a cluster with only 1 member and that seems to be reliably work. #128
/close
This seems to be an issue with etcd operator (coreos/etcd-operator#2163). For now, we are creating a cluster with only 1 member and that seems to be reliably work. #128
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When running the aws-installer for a 4.4 release, the etcd operator will fail to initialize a cluster if the etcdcluster CR is created asynchronously along with the etcd operator deployment. If a pause is added between the creation of the etcd operator and the etcdcluster CR, the problem goes away.
Investigate why this is an issue and update code appropriately
#120
The text was updated successfully, but these errors were encountered: