fix: keel-overlay-etcd depends on etcd-client (keel#83) #48
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/common!48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/etcd-client-for-keel"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The packaging half of Keel-Linux/keel#83: keel asks etcd with
etcdctlover gRPC, since etcd 3.5 maps a client certificate's CN to a user over gRPC only (its JSON gateway calls etcd with the member's own certificate and refuses CN-bearing client certificates once auth is on).etcd-client.${source:Version}equality is not possible here: etcd-client and etcd-server come from Debian'setcdsource, not this package's. So both are bounded to the same upstream release,(>= 3.5.16), (<< 3.5.17~). A new etcd upstream becomes a deliberate update of this package. This adds the upper bound to etcd-server as well.${source:Version}.keel#90 declares
Breaks: keel-overlay-etcd (<< 0.4.0~), and this package depends on keel (>= 0.22.0), the keel that asks etcd with etcdctl.