blob: c25736bae2cc4ece6a51214bec0ff74c8c0b7c24 [file] [log] [blame]
Lorenz Brundd8c80e2019-10-07 16:19:49 +02001// Copyright 2020 The Monogon Project Authors.
2//
3// SPDX-License-Identifier: Apache-2.0
4//
5// Licensed under the Apache License, Version 2.0 (the "License");
6// you may not use this file except in compliance with the License.
7// You may obtain a copy of the License at
8//
9// http://www.apache.org/licenses/LICENSE-2.0
10//
11// Unless required by applicable law or agreed to in writing, software
12// distributed under the License is distributed on an "AS IS" BASIS,
13// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14// See the License for the specific language governing permissions and
15// limitations under the License.
16
Hendrik Hofstadt0d7c91e2019-10-23 21:44:47 +020017syntax = "proto3";
Serge Bazanski662b5b32020-12-21 13:49:00 +010018package metropolis.proto.common;
Serge Bazanski31370b02021-01-07 16:31:14 +010019option go_package = "source.monogon.dev/metropolis/proto/common";
Hendrik Hofstadt0d7c91e2019-10-23 21:44:47 +020020
Serge Bazanski30653ee2021-06-17 15:44:29 +020021// NodeRoles are the possible roles that a Metropolis Node should run within the
22// cluster. These are configured by the cluster and can be retrieved through the
23// Curator.
Serge Bazanski5839e972021-11-16 15:46:19 +010024//
25// Fields contained within each individual are publicly available, so while they
26// can be used to carry required data to start up services for a given role,
27// this must not be confidential/private data.
Serge Bazanski30653ee2021-06-17 15:44:29 +020028message NodeRoles {
29 message KubernetesWorker {
30 }
Serge Bazanski5839e972021-11-16 15:46:19 +010031 message ConsensusMember {
32 // ca_certificate is a DER-encoded x509 certificate of the etcd
33 // cluster's CA. The member must use this certificate to verify the
34 // identity of the cluster it's connecting to.
35 bytes ca_certificate = 1;
36 // pper_certificate is a DER-encoded x509 certificate of this node's
37 // etcd peer listener. The member must serve member traffic using this
38 // certificate. The private key corresponding to this certificate is
39 // the same as the node's primary private keypair.
40 bytes peer_certificate = 2;
41 // initial_crl is a certificate revocation list that the etcd member
42 // should be started with. After startup, the member will maintain its
43 // own CRL by updating it from its primary storage location, and etcd
44 // value.
45 //
46 // TODO(q3k): don't pass this here, instead pass this over an etcd
47 // watcher and curator.Watch.
48 bytes initial_crl = 3;
49 message Peer {
50 string Name = 1;
51 string URL = 2;
52 }
53 repeated Peer peers = 4;
54 }
Serge Bazanski30653ee2021-06-17 15:44:29 +020055 KubernetesWorker kubernetes_worker = 1;
Serge Bazanski5839e972021-11-16 15:46:19 +010056 ConsensusMember consensus_member = 2;
Serge Bazanski30653ee2021-06-17 15:44:29 +020057}
58
59// NodeState is the state of a Metropolis node from the point of view of the
60// cluster it is a part of (or intending to be a part of).
61enum NodeState {
62 NODE_STATE_INVALID = 0;
63
64 // NEW: the node has established a first contact with the cluster and
65 // intends to register into it. The node's identity has not been verified
66 // and no hardware attestation of the new node was performed.
Mateusz Zalegad57ef1c2022-07-01 12:22:33 +020067 // The node has generated a CUK/NUK and set up storage encrypted with the
Serge Bazanski30653ee2021-06-17 15:44:29 +020068 // combination of both keys.
69 // The node has generated a private/public keypair, and that keypair has
70 // been used to contact the already running Cluster.
71 NODE_STATE_NEW = 1;
72 // STANDBY: the node has successfully passed identity and hardware
73 // attestation checks as defined by the cluster policy. The node still isn't
74 // part of the cluster, as it itself might perform checks against the
75 // running Cluster.
76 NODE_STATE_STANDBY = 2;
77 // UP: the node has passed all preconditions for STANDBY and has also
78 // performed a commit into the cluster by exchanging its CUK for a
79 // certificate issued by the cluster.
80 // The node is now ready to serve, and its certificate can be used to
81 // authenticate its identity cryptographically.
82 NODE_STATE_UP = 3;
83 // DISOWNED: the node has been rejected or decommissioned by the cluster.
84 // Any further contact from the node to the cluster will be rejected.
85 NODE_STATE_DISOWNED = 4;
86};
87
88// ClusterState is the state of the cluster from the point of view of a node.
89// Different subsystems can watch this state and depend on it for behaviour
90// (eg. start serving when HOME, maybe self-fence on SPLIT, etc.).
91enum ClusterState {
92 CLUSTER_STATE_INVALID = 0;
93
94 // UNKNOWN: the node has not yet determined the existence of a cluster it
95 // should join or start. This is a transient, initial state that should only
96 // manifest during boot.
97 CLUSTER_STATE_UNKNOWN = 1;
98 // FOREIGN: the node is attempting to register into an already existing
99 // cluster with which it managed to make preliminary contact, but which the
100 // cluster has not yet fully productionized (eg. the node is still being
101 // hardware attested, or the operator needs to confirm the
102 // registration of this node).
103 CLUSTER_STATE_FOREIGN = 2;
104 // TRUSTED: the node is attempting to register into an already registered
105 // cluster, and has been trusted by it. The node is now attempting to fully
106 // commit to registering into the cluster.
107 CLUSTER_STATE_TRUSTED = 3;
108 // HOME: the node is part of this cluster. This is the bulk of time in which
109 // this node will spend its time.
110 CLUSTER_STATE_HOME = 4;
111 // DISOWNING: the node has been disowned (ie., removed) by the cluster, and
112 // that it will not be ever part of any cluster again, and that it will be
113 // decommissioned by the operator.
114 CLUSTER_STATE_DISOWNING = 5;
115 // SPLIT:the node would usually be Home in a cluster, but has been split
116 // from the consensus of the cluster. This can happen for nodes running
117 // consensus when consensus is lost (eg. when there is no quorum or this
118 // node has been netsplit), and for other nodes if they have lost network
119 // connectivity to the consensus nodes. Clients should make their own
120 // decision what action to perform in this state, depending on the level of
121 // consistency required and whether it makes sense for the node to fence its
122 // services off.
123 CLUSTER_STATE_SPLIT = 6;
124}
Serge Bazanski2893e982021-09-09 13:06:16 +0200125
126// NodeStatus contains all fields self-reported by nodes. This data is
127// inherently less trusted than other data available about a node, as it can be
128// updated to any value by each node individually, including compromised nodes.
129message NodeStatus {
130 // external_address is the IP address that the node expects management,
131 // cluster and user traffic to arrive at (ie. the address on which it is
132 // listening for gRPC, and role-specific services like etcd and
133 // Kubernetes).
134 string external_address = 1;
Serge Bazanski966d40c2022-06-23 13:27:16 +0200135 // running_curator contains information about the curator service running
136 // on this node, or is nil if the service is not running.
137 message RunningCurator {
138 // port is the TCP port on which the curator is listening.
139 int32 port = 1;
140 }
141 RunningCurator running_curator = 3;
Mateusz Zalega312a2272022-04-25 12:03:58 +0200142 // timestamp is an epoch number associated with the last status update.
143 // It's set with a nanosecond granularity.
144 int64 timestamp = 2;
Serge Bazanski2893e982021-09-09 13:06:16 +0200145}
146
147// The Cluster Directory is information about the network addressing of nodes
148// in a cluster. It is a serialized snapshot of some of the state within the
149// etcd cluster, and can be used by external processes (like a node Registering
150// into the cluster) to know how to reach this cluster over the network. It can
151// be thought of as a phonebook, or a static name/address configuration that
152// could live in /etc/hosts.
153//
154// The directory explicitly doesn't carry any information about the cluster's
155// identity or security - these should be configured and checked by higher
156// level configuration and processes. The directory can be stored and
157// transmitted in cleartext and without an integrity checks (like saved to the
158// EFI system partition across reboots) and any malicious change to it will
159// cause no more than a denial of service against the consumer of this
160// directory. This is because all nodes contacted must present a valid cluster
161// identity/certificate before they are trusted by the consumers of this
162// directory.
163message ClusterDirectory {
164 message Node {
165 bytes public_key = 1;
166 message Address {
167 string host = 1;
168 };
Serge Bazanskibc671d02021-10-05 17:53:32 +0200169 repeated Address addresses = 2;
Serge Bazanski2893e982021-09-09 13:06:16 +0200170 };
171 repeated Node nodes = 1;
172}