Fixing SDS field/semantics in the gateway

networking/v1alpha3/gateway.proto

@@ -304,6 +304,18 @@ message Server {
     // client side certificate.
     string ca_certificates = 5;
 
+    // The credentialName stands for a unique identifier that can be used
+    // to identify the serverCertificate, the privateKey and the
+    // CaCertificates associated with this server. Gateway workloads
+    // capable of fetching credentials from a remote credential store will
+    // be configured to retrive the credentials using this name, instead of
+    // using the file system paths specified above. The semantics of the
+    // name are platform dependent. In Kubernetes, the default Istio
+    // supplied credentail server expects the credentialName to match the
+    // name of the Kubernetes secret that holds the server certificate, the
+    // private key, and the CA certificate (if using mutual TLS).
+    string credential_name = 10;
+
     // A list of alternate names to verify the subject identity in the
     // certificate presented by the client.
     repeated string subject_alt_names = 6;

proto.lock

@@ -3323,6 +3323,11 @@
                     "name": "ca_certificates",
                     "type": "string"
                   },
+                  {
+                    "id": 10,
+                    "name": "credential_name",
+                    "type": "string"
+                  },
                   {
                     "id": 6,
                     "name": "subject_alt_names",